Fix FN for invalid-name for type-annotated module constants
#112
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
CodSpeed Performance ReportMerging #112 will not alter performanceComparing Summary
|
art049
force-pushed
the
upstream/invalid-name-type-annotation
branch
from
f33262e to
4035baa
Compare
art049
force-pushed
the
upstream/invalid-name-type-annotation
branch
from
4035baa to
2811003
Compare
art049
force-pushed
the
main
branch
9 times, most recently
from
95f9144 to
4a822ba
Compare
art049
force-pushed
the
main
branch
9 times, most recently
from
671b8a5 to
50af598
Compare
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 pull request was created automatically by CodSpeed to track performance changes of the pull request pylint-dev/pylint#9771.
The original branch is upstream/invalid-name-type-annotation