Avoid setting enable-frozen-string-literal RUBYOPT for Ruby 3.4 in the CI
#496
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This flag was redundant for our own code since we already have the `# frozen_string_literal: true` directive at the top of each file, enforced by RuboCop. While the flag could theoretically catch frozen string issues in dependencies, I don't think we want our CI to fail because of frozen string errors in gems we don't have control of.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This flag is redundant for our own code since we already have the
# frozen_string_literal: truedirective at the top of each file, enforced by RuboCop.While the flag could theoretically catch frozen string issues in dependencies, I don't think we want our CI to fail because of frozen string errors in gems we don't have control of.