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
I love that this library exists but I'm struggling to put it into practice.
As of now, my linter (mypy and ruff, on vs code) don't check or warn about incorrect annotations and behaviors, so I'm getting all failures at once when I try to run test discovery in pytest.
Can I directly check "correctness" while writing, via a linter?
If anyone can point me in the right direction, and if it would be helpful for other new users, I'm happy to submit a PR with the guidance here. :)
Also - and perhaps just as important - I'm seeing failures during test discovery, which is a horrible time to fail because it breaks the IDE's test UI. Can I defer this when discovering my tests (at minimum) and then get them at runtime?
The text was updated successfully, but these errors were encountered:
aaronsteers
changed the title
Docs request: guidance re: IDE linting?
Docs request: IDE linting guidance
Dec 21, 2023
I love that this library exists but I'm struggling to put it into practice.
As of now, my linter (mypy and ruff, on vs code) don't check or warn about incorrect annotations and behaviors, so I'm getting all failures at once when I try to run test discovery in
pytest
.Can I directly check "correctness" while writing, via a linter?
If anyone can point me in the right direction, and if it would be helpful for other new users, I'm happy to submit a PR with the guidance here. :)
Also - and perhaps just as important - I'm seeing failures during test discovery, which is a horrible time to fail because it breaks the IDE's test UI. Can I defer this when discovering my tests (at minimum) and then get them at runtime?
The text was updated successfully, but these errors were encountered: