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
rescue StandardError => e1 begin @logger.fatal "EXCEPTION: #{e1}" rescue StandardError => e2 printf "\nFATAL: Several exceptions\n#{e1}\n\n#{e2}\n" end end
I want to log e1 and e2, but rubocop tranforms this code in
rescue StandardError => e1 begin @logger.fatal "EXCEPTION: #{e1}" rescue StandardError => e1 printf "\nFATAL: Several exceptions\n#{e1}\n\n#{e1}\n" end end
so only last exception will be printed, and I can only use one prefered name of exceptions
$ [bundle exec] rubocop -V 1.11.0 (using Parser 3.0.0.0, rubocop-ast 1.4.1, running on ruby 2.7.2 x86_64-linux) - rubocop-rake 0.5.1
The text was updated successfully, but these errors were encountered:
Naming/RescuedExceptionsVariableName
[Fix rubocop#9586] Update Naming/RescuedExceptionsVariableName to n…
11321c1
…ot register on inner rescues when nested.
Merge pull request #9587 from dvandersluis/issue/9586
c2154be
[Fix #9586] Update `Naming/RescuedExceptionsVariableName` to not register on inner rescues when nested.
Successfully merging a pull request may close this issue.
I want to log e1 and e2, but rubocop tranforms this code in
so only last exception will be printed, and I can only use one prefered name of exceptions
RuboCop version
The text was updated successfully, but these errors were encountered: