I updated docs with string interpolation with an explicit example. It's not quite like the initial issue report where the colon came from the variable but it should get the point across.
Before submitting the PR make sure the following are checked:
[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] 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.
koic
commented
10 months ago
As per my findings in https://github.com/rubocop/rubocop-performance/pull/427#issuecomment-1865914939
I updated docs with string interpolation with an explicit example. It's not quite like the initial issue report where the colon came from the variable but it should get the point across.
Before submitting the PR make sure the following are checked:
[Fix #issue-number](if the related issue exists).master(if not - rebase it).bundle exec rake default. It executes all tests and runs RuboCop on its own code.{change_type}_{change_description}.mdif the new code introduces user-observable changes. See changelog entry format for details.