-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project wide evaluation #79
Comments
I would also find it cool if you could either do folder or maybe just workspace linting. |
I seem to have imagined it, but apparently pylint in the python extension did not react to |
I would love to see it as well.
Please consider implementing this |
Pylint can evaluate code across a folder and subfolders, which provides insights into issues such as duplicate code. Being able to trigger pylint on a folder can provide users with a unique feature not available in the built-in linting of the vscode python extension. Additionally, users could apply this to gain insights into a project's general code quality, preferably by means of pylint's scoring feature.
The text was updated successfully, but these errors were encountered: