Add frozen_string_literal: true
in order to suppress 'warning: literal string will be frozen in the future'
#4599
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.
Which issue(s) this PR fixes:
Fixes #
What this PR does / why we need it:
To supress
warning: literal string will be frozen in the future
,we will require to fix with following proposals.
# frozen_string_literal: true
in the beginning of the file# frozen_string_literal: false
in the beginning of the fileRUBYOPT="-disable=frozen_string_literal"
as launch optionThese suggestions may be combined.
This PR adds
# frozen_string_literal: true
to all required files.Seems CI will be passed,
however, Fluentd might raise
FrozenError
exception by unexpected frozen stringif it has not sufficient test suites...
Related to GH-4585
Docs Changes:
Release Note: