-
-
Notifications
You must be signed in to change notification settings - Fork 763
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
Extend reserved name check #2886
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution.
Looks mostly good, a few minor tweaks, and I'm happy to merge it.
Please feel free to add a Changelog.md entry.
1.8.7/1.9.2 CI failures are apparently due to |
Can you rebase this? The build was updated with a ruby gems fix which means most legacy rubies should run now |
Still red due to RubyGems. |
Er apparently I hadn't merged those PRs that mostly fixed CI, my apologies, please rebase from latest main and try again 😹 |
Thanks, I'm pretty confident the remaining failures are existing build issues. |
…er-names Extend reserved name check
…-reserved-memoized-helper-names Extend reserved name check --- This commit was imported from rspec/rspec-core@fa1b5f5.
This commit was imported from rspec/rspec-core@04d5e52.
…-reserved-memoized-helper-names Extend reserved name check --- This commit was imported from rspec/rspec-core@6f8ee75.
This commit was imported from rspec/rspec-core@780580b.
Description
Fixes rspec/rspec-rails#2478
to_s
is now also viewed as a reserved name and thus may not be used.This also extends the name check to check against strings rather than just symbols.