Skip to content
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

Docs request: IDE linting guidance #120

Open
aaronsteers opened this issue Dec 21, 2023 · 1 comment
Open

Docs request: IDE linting guidance #120

aaronsteers opened this issue Dec 21, 2023 · 1 comment

Comments

@aaronsteers
Copy link

aaronsteers commented 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?

@aaronsteers aaronsteers changed the title Docs request: guidance re: IDE linting? Docs request: IDE linting guidance Dec 21, 2023
@aaronsteers
Copy link
Author

aaronsteers commented Dec 21, 2023

Looks like there's an open feature request for this in Ruff here:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant