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
Railties updates for frozen string literals. #29891
Railties updates for frozen string literals. #29891
Conversation
r? @schneems (@rails-bot has picked a reviewer for you, use r? to override) |
Also, @kirs: is this the last piece of the Rails puzzle that needs the pragma comment? Or are there other parts of Rails that still need some attention? |
Can you add the frozen string literals to the changed files? |
Hi @pat. Thanks for great work. It is a note related to this PR. After rebasing with the latest master branch, you can remove Style/FrozenStringLiteralComment:
Enabled: true
EnforcedStyle: always
Include:
Exclude:
- - 'railties/**/*'
- 'actionview/test/**/*.builder'
- 'actionview/test/**/*.ruby'
- 'actionpack/test/**/*.builder'
- 'actionpack/test/**/*.ruby' Please look when adding frozen string literal magic comments. |
Looks like Railties is the last component that's left to complete the migration to frozen string literal 💯 |
ab40a44
to
7f6a314
Compare
LGTM ❤️ |
Thanks @rafaelfranca! |
Updates to railties for frozen-string-literals compatibility.
It's worth noting that there are dependencies on the following libraries that aren't yet compatible:
When the above patches are in play, then the tests pass with
RUBYOPT="--enable-frozen-string-literal"
./cc @kirs given you're doing a lot of this work too!