-
Notifications
You must be signed in to change notification settings - Fork 87
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
[Closes #236] Operator space false positive #259
[Closes #236] Operator space false positive #259
Conversation
{string, _} -> []; | ||
{char, _} -> []; | ||
{comment, _} -> []; | ||
{_, string} -> []; |
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.
Why matching all this cases? If I'm not mistaken it would either be undefined
or any of your valid options. Wouldn't matching undefined and have an otherwise default behaviour save lines?
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.
We have to check for those types of nodes or tokens where an operator without a space is acceptable. An alternative would be to match for all that shouldn't have it, but in either case there needs to be an explicit specification of the valid (or invalid) types of nodes/tokens.
…positive [Closes #236] Operator space false positive
#236