Disable LC003 and LC005 for DotNet var/param names #119
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
|
Thanks for looking into this. I need to be honest that dotnet is not at the top of my list. Would it be okay for you if we close #95 with this fix/workaround? |
|
Yes, that is fine. 😊 |
rvanbekkum
deleted the
feature/95-disable-check-for-dotnet-variable-and-parameter-names
branch
StefanMaron
pushed a commit
that referenced
this pull request
Jan 5, 2022
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.
For the time being, until #95 gets resolved in a better way, this PR will disable the checks for variables, parameters and also return variable names with DotNet as data type (even though the latter cannot have
DotNetas data-type).Note that the check for the casing of
DotNetitself still works, but the subtype check is skipped.