Navigation Menu

Skip to content
New issue

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

Support in pattern syntax for Layout/CaseIndentation #9818

Conversation

koic
Copy link
Member

@koic koic commented May 24, 2021

This PR supports Ruby 2.7's in pattern syntax for Layout/CaseIndentation. It is extending Layout/CaseIndentation cop because I think it's expected that the indentation layout will be the same for case ... when and case ... in.


Before submitting the PR make sure the following are checked:

  • The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
  • Wrote good commit messages.
  • Commit message starts with [Fix #issue-number] (if the related issue exists).
  • Feature branch is up-to-date with master (if not - rebase it).
  • Squashed related commits together.
  • Added tests.
  • Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
  • Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

This PR supports Ruby 2.7's `in` pattern syntax for `Layout/CaseIndentation`.
It is extending `Layout/CaseIndentation` cop because I think it's expected
that the indentation layout will be the same for `case ... when` and `case ... in`.
@bbatsov
Copy link
Collaborator

bbatsov commented May 25, 2021

Looks good. Thanks!

@bbatsov bbatsov merged commit 4216c38 into rubocop:master May 25, 2021
@koic koic deleted the support_in_pattern_syntax_for_layout_case_indentation branch May 25, 2021 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants