-
Notifications
You must be signed in to change notification settings - Fork 1.8k
similar_names
stop linting for 3-char names
#15100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
r? @lyxyas |
Failed to set assignee to
|
you probably meant blyxyas? |
sure or anybody that can review |
r? @blyxyas |
Hi @honeyspoon, thanks for pinging me, I'll review it as soon as I have the time (I have some more reviews in queue and I'm currently writing a Project Goal). Thanks for contributing! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks! ❤️
Sorry for the slow review, and welcome to the project. Could you squish the 3 commits into one?
Lintcheck changes for e41fb7c
This comment will be updated if you push new changes |
thanks I just squashed |
fixes #14869
Added a simple check if both chars are of length 3
If they are, we skip the check for that pair.
This won't handle the 4 v 3 case.
Not sure if this was the intent of the issue.
Also saw we have some hardcoded exemptions for
set, get
andlhs, rhs
Tried removing them thinking they would be handled by the new condition.
But we have to keep because they allow for
bla_lhs
vbla_rhs
to be skippedchangelog:[
similar_names
]: Stop triggering for 3-character names