feat: Enable pylints' invalid name rule C0103 #1461
Merged
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 enables pylints' invalid-name rule, i.e., C0130 and fixes resulting issues. One issue was properly fixed by changing constant enum fields to uppercase and two other issues were simply ignored. The first ignored issue, i.e., the naming problem of
T4CRepositoriesResponseModel
is not compliant due to the two directly preceding capital lettersCR
, which is intended here. The second problem is a false positive, sincepod_security_context
is considered a constant, but there are two places where we assign it a value, i.e., it is not actually constant.Resolves #1379