-
-
Notifications
You must be signed in to change notification settings - Fork 158
Implement LeadingCharacterFixer #259
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
Delimiters occur between other characters, not at the beginnings of words, so I updated that and removed a test case (it was also interfering with LeadingCharacterFixer).
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.
@baile320 👋 Thank you for your contribution! 🚀
I have left some comments. Please take a look at them 👀
Good catch! Thank you! 👍
@evgeniy-r is already working on that feature (#252) 💪 |
… into leading-char-fixer
Bug was introduced into IncorrectDelimiterChecker in previous commit where "*FOO-BAR=VALUE" would not have risen a warning. Additionally, LeadingCharacterFixer would not remove all invalid leading chars, just one. This has also been fixed.
|
I merged in the changes from #267 and made some other relatively minor changes related to test names, checks, formatting. I think this PR is ready to go or be re-reviewed! Thanks! |
Co-authored-by: Grachev Mikhail <work@mgrachev.com>
… into leading-char-fixer
…nv-linter into leading-char-fixer
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 👍
|
@baile320 Thanks a lot! You're awesome! ❤️ |
This will close: #248
I have a couple comments/questions:
✔ Checklist: