Skip to content

Conversation

chaadow
Copy link

@chaadow chaadow commented Jan 26, 2025

Fixes #1429


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.
  • If this is a new cop, consider making a corresponding update to the Rails Style Guide.
@chaadow chaadow force-pushed the fix_expect_param_recursive branch 2 times, most recently from 2af9715 to 1b8d885 Compare January 26, 2025 11:52
user: [:name, # comment
:age] # comment
)
user: [:name, :age])
Copy link
Author

@chaadow chaadow Jan 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could not find a solution to preserve comments when autocorrecting in a recursive fashion

Fixes rubocop#1429 Use a recursive approach to autocorrect nested parameters - Top level hash keys do not get replaced by `[]` - Hash values that are hashes get replaced by `[]` - Arrays get replaced by double brackets `[[]]`
@chaadow chaadow force-pushed the fix_expect_param_recursive branch from 1b8d885 to 7e12bd2 Compare January 26, 2025 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant