fix: avoid early return in used_type_checking_imports#123
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## main #123 +/- ##
=====================================
Coverage 98.7% 98.7%
=====================================
Files 3 3
Lines 466 469 +3
=====================================
+ Hits 460 463 +3
Misses 6 6
|
Member
Contributor
Author
|
@sondrelg Thanks, sounds good! I'm in no rush to get these fixes into a release, so take your time 😄 |
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
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.
This PR prevents false negatives for TC004, which were caused by
used_type_checking_importsreturning immediately on the first function-scoped import usage, and therefore not warning about TC004 errors that would have followed.I don't think this can be reproduced/tested reliably, as it depends on the order in which the
type_checking_block_importsset is iterated over, and AST node hashes arbitrarily change which results in different iteration orders over subsequent flake8 runs.Reproduction