You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some reason, I find that the type-checker extension is showing stale results in the editor. But when I go to the output window and run the command that is being logged in my own shell, I get the correct and expected answer. This seems to happen when changes are made in another file than the one being viewed/edited.
If you have mypy-type-checker.reportingScope set as file then we don’t update the results for all files. It only updates results for the file you are working on. Set it to workspace.
lemme see if that makes it better. Though I will say these edits usually come through other tabs in the same window. -e- (not a great solution for a large production codebase, as that increases runtime substantially)
For some reason, I find that the type-checker extension is showing stale results in the editor. But when I go to the output window and run the command that is being logged in my own shell, I get the correct and expected answer. This seems to happen when changes are made in another file than the one being viewed/edited.
For example:
Using
v2023.7.13181008
(latest pre-release), with the settings:And my
mypy-type-checker
points to the mypy in the python venv set for the project.The text was updated successfully, but these errors were encountered: