We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug When matching ruby code expression names that contain _for are valid matches to not match
_for
Reproducing bit.ly/3Hezuwj
When bla_for is replaced with blafor the above example does match
bla_for
blafor
Expected behavior I expected the above example (without modification) to match.
Additional context It seems the _for in the expression name is being parsed as a delimiter
The text was updated successfully, but these errors were encountered:
yep, this is wrong behavior. thanks for the report, will have a look at a fix!
Sorry, something went wrong.
Also seeing similar behavior with do_
do_
bit.ly/3diyFsl
Same in Elixir with end for example: bit.ly/3NE5nSR
end
No branches or pull requests
Describe the bug
When matching ruby code expression names that contain
_for
are valid matches to not matchReproducing
bit.ly/3Hezuwj
When
bla_for
is replaced withblafor
the above example does matchExpected behavior
I expected the above example (without modification) to match.
Additional context
It seems the
_for
in the expression name is being parsed as a delimiterThe text was updated successfully, but these errors were encountered: