-
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
No visual indication of mypy linting errors #1440
Comments
@brettcannon Speaking of squiggles, I find them a bit too shy and modest in their attempt to bring my attention to the potential problem (especially red squiggles). They are like: "erm, Sir, sorry to disturb you, but there is something you might want to look at", while I'd like them to be more of a: "ERMAHGERD!! THIS INSTANCE DOES NOT HAVE THIS METHOD!! DO SOMETHING ABOUT IT NOW OTHERWISE WE ALL DIE!!!". I mean, I wish red squiggles were a bit more apparent and hard to miss. Yes, they are also marked in the scrollbar, but there they are also a bit tiny. Can errors paint current line in gutter red as well? Or is there an option to increase the line width of the squiggle? |
We could use the gutter, but that would be inconsistent with the rest of vscode. This is something you'll have to raise on the vscode repo. |
Hi, I am also facing this issue.
I see all the output correctly in the Output tab:
However there are no Problems reported or squiggly lines shown. |
@eeyang92 please open a separate issue. |
Environment data
Actual behavior
Linting errors from output not displayed visually (no red, squiggly underlining or recognized issues in Problems tab).
Expected behavior
Expect visual indication (in underlining and Problems tab) of mypy linting errors.
Steps to reproduce:
'hi' + 1
(or anything that should trigger a linting error)Logs
Seems to maybe be related to these issues (though those issues were marked fixed) - #343 & #245
The text was updated successfully, but these errors were encountered: