add new rules for ease of use: pascalcaseacronym, uppercasedigit #225
Conversation
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
1 participant
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.
Hello.
Proposing two tiny rules.
PascalCaseAcronym that allows for up to five consecutive uppercase letters.
It (not directly perhaps) has been sought after not by me alone judging by this and that.
UppercaseDigit that would help with stuff like VINs etc. ([A-Z0-9]+ is not sufficient as I have cyryllic symbols, regex is not elegant)
I thank you for your work, tool's cool.
Whatever your word's on the pull cap.