Skip to content

Fix Lint/LiteralInInterpolation cop error on invalid string literal #13603

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

Conversation

viralpraxis
Copy link
Contributor

@viralpraxis viralpraxis commented Dec 18, 2024

echo '"#{"\201\203"}"' | rubocop --stdin bug.rb --only Lint/LiteralInInterpolation -d

An error occurred while Lint/LiteralInInterpolation cop was inspecting bug.rb:1:0.
invalid byte sequence in UTF-8
lib/active_support/core_ext/object/blank.rb:159:in `match?'
lib/active_support/core_ext/object/blank.rb:159:in `blank?'
lib/rubocop/cop/lint/literal_in_interpolation.rb:171:in `space_literal?'
lib/rubocop/cop/lint/literal_in_interpolation.rb:51:in `offending?'
lib/rubocop/cop/lint/literal_in_interpolation.rb:26:in `on_interpolation'

Co-authored-by: Koichi ITO koic.ito@gmail.com


Before submitting the PR make sure the following are checked:

  • The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
  • Wrote good commit messages.
  • Commit message starts with [Fix #issue-number] (if the related issue exists).
  • Feature branch is up-to-date with master (if not - rebase it).
  • Squashed related commits together.
  • Added tests.
  • Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
  • 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.

@viralpraxis viralpraxis force-pushed the fix-lint-literal-in-interpolation-error-on-invalid-string branch from 913d505 to 6ea3ddc Compare December 19, 2024 15:28
@viralpraxis viralpraxis force-pushed the fix-lint-literal-in-interpolation-error-on-invalid-string branch from 6ea3ddc to 245db4d Compare December 20, 2024 10:02
```console
echo '"#{"\201\203"}"' | rubocop --stdin bug.rb --only Lint/LiteralInInterpolation -d

An error occurred while Lint/LiteralInInterpolation cop was inspecting bug.rb:1:0.
invalid byte sequence in UTF-8
lib/active_support/core_ext/object/blank.rb:159:in `match?'
lib/active_support/core_ext/object/blank.rb:159:in `blank?'
lib/rubocop/cop/lint/literal_in_interpolation.rb:171:in `space_literal?'
lib/rubocop/cop/lint/literal_in_interpolation.rb:51:in `offending?'
lib/rubocop/cop/lint/literal_in_interpolation.rb:26:in `on_interpolation'
```

Co-authored-by: Koichi ITO <koic.ito@gmail.com>
@viralpraxis viralpraxis force-pushed the fix-lint-literal-in-interpolation-error-on-invalid-string branch from 245db4d to 0d12b17 Compare December 21, 2024 08:59
@koic koic merged commit 0d61421 into rubocop:master Dec 21, 2024
22 checks passed
@koic
Copy link
Member

koic commented Dec 21, 2024

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy