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
Message: Style/EvalWithLocation: Use __LINE__ - 3 instead of __LINE__, as they are used by backtraces.
Style/EvalWithLocation: Use __LINE__ - 3 instead of __LINE__, as they are used by backtraces.
Message: Style/EvalWithLocation: Use __LINE__ - -3 instead of __LINE__, as they are used by backtraces.
Style/EvalWithLocation: Use __LINE__ - -3 instead of __LINE__, as they are used by backtraces.
Note: The line offset would be +3 if you followed the message.
+3
eval('puts 42', binding, __FILE__, __LINE__)
Include the output of rubocop -V. Here's an example:
rubocop -V
$ rubocop -V 0.52.0 (using Parser 2.4.0.2, running on ruby 2.4.1 x64-mingw32)
The text was updated successfully, but these errors were encountered:
[Fix rubocop#5273] Fix Style/EvalWithLocation reporting bad line of…
Style/EvalWithLocation
1132ef8
…fset See rubocop#5273 Cause ==== I forgot an `abs`. 🙇
6fb5a84
No branches or pull requests
Expected behavior
Message:
Style/EvalWithLocation: Use __LINE__ - 3 instead of __LINE__, as they are used by backtraces.
Actual behavior
Message:
Style/EvalWithLocation: Use __LINE__ - -3 instead of __LINE__, as they are used by backtraces.
Note: The line offset would be
+3
if you followed the message.Steps to reproduce the problem
RuboCop version
Include the output of
rubocop -V
. Here's an example:The text was updated successfully, but these errors were encountered: