Yudai Takada
Yudai Takada
It appears to me that they are follow-up the documentation of different cases. https://github.com/rubocop/rubocop/pull/10868 appear to want to prevent misleading about the following cases: ```ruby # before foo || raise('exception')...
The title and text of this PR have been updated. What do you think?
I updated this PR. Thank you so much.
That behavior seems correct. `Style/GuardClause` cop is offense for conditional branches with if-else if the body of the condition contains `return` or `break` or `next` or `raise` or `fail`. Therefore,...
`Gemspec/DateAssignment` will be merged into `Gemspec/DeprecatedAttributeAssignment` in the future. However, the integration is pending because RuboCop 1.x does not allow breaking changes. PRs that have implemented this change include -...
@mlwyatt I'm currently working on this issue. I'd like to know about the cases in which the not allow multiple elements per line to`%` literals array caused problems.
I updated this PR. Thank you so much.
I updated this PR. Thank you so much.
```ruby # bad find('#some-id a.some-class').click # good find('#some-id').click_link(class: 'some-class') ``` In the above case, it looked good as new another cop like a `RSpec/Capybara/SpecificActions`. ref: https://rubydoc.info/github/jnicklas/capybara/master/Capybara%2FNode%2FActions:click_link
```ruby # bad find('#some-id') # good find_by_id('some-id') ``` And in the above case, also new cop like a `RSpec/Capybara/SpecificFinders` ? ref: https://rubydoc.info/github/jnicklas/capybara/Capybara/Node/Finders