Resolve all pyright reportMissingImports#2420
Draft
Avasam wants to merge 12 commits intomhammond:mainfrom
Draft
Conversation
…ve-pyright-reportMissingImports
…ve-pyright-reportMissingImports
…ve-pyright-reportMissingImports
Avasam
force-pushed
the
Resolve-pyright-reportMissingImports
branch
from
1c810ee to
e44f630
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Still opening as draft, but I don't think it'll be worth the added complexity, most of these imports get exposed publicly or used locally in a way that could reveal potential issues. Except adsi, since that one re-exports everything it will bring value.
Merging #2282 first should reduce some changes