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
rubocop (0.32.1)
with these settings:
BlockDelimiters: Enabled: true EnforcedStyle: semantic
To reproduce:
rubocop -a on the following code:
rubocop -a
h[i] = [predecessor.detect { |j| j[key] == i }, current.detect { |j| j[key] == i }]
will incorrectly flag an offense:
example.rb:1:30: C: [Corrected] Prefer do...end over {...} for procedural blocks. h[i] = [predecessor.detect { |j| j[key] == i },
and rewrite the code as such:
h[i] = [predecessor.detect do |j| j[key] == i end, current.detect { |j| j[key] == i }]
The text was updated successfully, but these errors were encountered:
Fix syntax (w/Rubocop) in (Rails) models
df51b6e
Signed-off-by: Alex Coles <alex@alexbcoles.com>
Fix bad rubocop auto-correct in journal_manager.rb
8fd5357
Reported as issue upstream: rubocop/rubocop#2021 [ci skip] Signed-off-by: Alex Coles <alex@alexbcoles.com>
/ @NobodysNightmare
Sorry, something went wrong.
c9dbfce
Merge pull request #2046 from lumeet/2021_semantic_block_in_array
13308bd
[Fix #2021] Allow semantic block in array or range
No branches or pull requests
Environment
rubocop (0.32.1)
with these settings:
Issue
To reproduce:
rubocop -a
on the following code:will incorrectly flag an offense:
and rewrite the code as such:
The text was updated successfully, but these errors were encountered: