-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Support the "Info" category for flake8 #1438
Comments
We should come up with a flexible mechanism for classifying flake8 issues/categories so that we can cover this need as well as any other future categories a plug-in might add. Idea I head was a dict whose keys get put into a trie which we can the use to find the specified category or issue's classification. |
This ought to work if the flake8 plugin uses more than 1 letter for the prefix, e.g.
does not work (you have to use |
Similar case for
thus generates
In case someone has the same issue: Put the following in the settings to remap these to errors:
But of course, if you have another flake-8 plugin that generates error codes starting with |
To extend on this, I would like to be able to do "python.linting.flake8CategorySeverity.SIM": "Warning",
"python.linting.flake8CategorySeverity.SIM9": "Information", |
Please try the One of the things you can do there is customize the severity, by individual error codes or categories. |
Closing this, since we have begun to process to migrate users over to |
Relevant equivalent issue on the new repo. In case anyone comes across this. Go there instead: microsoft/vscode-flake8#7 |
Environment data
flake8==3.5.0
flake8-import-order==0.17.1
Actual behavior
Flake8 plugin configuration settings don’t match the settings schema in vscode, even though the settings do work.
Expected behavior
Flake8 plugin settings are not marked as unknown in the vscode settings file.
Steps to reproduce:
Install
flake8
Install
flake8-import-order
Open a file with the following contents:
Notice how this triggers an info level problem
Add this line to your vscode settings:
Notice this gives a warning in the settings file
Save or reopen the Python file
Notice that the severity level has changed from info to warning
Logs
N/A
The text was updated successfully, but these errors were encountered: