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

Make Lint/UselessAccessModifier aware of Ruby 3.2's Data.define #11546

Conversation

koic
Copy link
Member

@koic koic commented Feb 7, 2023

Ruby 3.2 introduced immutable Data.define. Since this is similar to Struct.new. This Lint/UselessAccessModifier will handle Struct.new and Data.define in the same way.


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.

Ruby 3.2 introduced immutable `Data.define`. Since this is similar to `Struct.new`.
This `Lint/UselessAccessModifier` will handle `Struct.new` and `Data.define` in the same way.
@koic koic force-pushed the make_useless_access_modifier_aware_of_data_define branch from 35720e6 to a13587b Compare February 7, 2023 09:53
@bbatsov bbatsov merged commit f7eae2c into rubocop:master Feb 8, 2023
@bbatsov
Copy link
Collaborator

bbatsov commented Feb 8, 2023

Thanks!

@koic koic deleted the make_useless_access_modifier_aware_of_data_define branch February 8, 2023 11:00
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