specify __all__ for type checkers #83
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Sure 👍🏻 Please just run the precommit / black to fix the whitespace and I'll merge. |
In the following use, pyright gets unhappy ``` from rich_click import click @click.option ``` Being explicit in __all__ makes it happy (see rules here https://github.com/microsoft/pyright/blob/main/docs/typed-libraries.md#library-interface)
ajparsons
force-pushed
the
all-for-typecheckers
branch
from
403f0af
to
8d36902
Compare
|
Doh - fixed. |
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the following use, pyright gets unhappy (reportPrivateImportUsage) about option because it was imported from click.
Being explicit in
__all__makes it happy(see rules here https://github.com/microsoft/pyright/blob/main/docs/typed-libraries.md#library-interface)