This repository was archived by the owner on Oct 11, 2021. It is now read-only.
refactor: use UPPER_CASE for Enum members#499
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #499 +/- ##
=======================================
Coverage 89.27% 89.27%
=======================================
Files 22 22
Lines 3338 3338
Branches 845 845
=======================================
Hits 2980 2980
Misses 194 194
Partials 164 164
Flags with carried forward coverage won't be shown. Click here to find out more.
|
This is required since pylint 2.7.0
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Pylint 2.7.0 now checks whether members of an
Enumare UPPER_CASEhttp://pylint.pycqa.org/en/latest/whatsnew/changelog.html#what-s-new-in-pylint-2-7-0
Automated changes by create-pull-request GitHub action