-
Notifications
You must be signed in to change notification settings - Fork 48
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
ci: validate import statements in modules #204
Conversation
This reverts commit aa7ad9d.
Pyright already validates imports. What exactly are you trying to achieve? |
I'm looking to validate imports but merging the import changes. Yeah, pyright would be better. Would you just rename the project directory then run it? I get reportMissingImports errors doing it that way? |
Yeah, I want to merge 200 after having this check is in the CI. Because in 200, pyright isn't in yet. |
We could merge pyright and limit it's scope / files to something that works for us. If it's only about the imports, we could just use the rules for the imports I guess. Meanwhile #152 is the prove, that #200 is fine in regards of it's imports. The CI already verified them, as Pyright is active there and #200 is just a cherry-picked subset. EDIT: |
Mind referencing the docs for that? I can't find info about that value. |
Well, in any case, I want to get this in for now. We can remove it later for pyright, which is faster. |
Sure. I created PR #205, just have a look. It currently annotates the imports and flags it as a warning, but we could let the CI fail. About the documentation: |
No description provided.