Skip to content
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

ImplicitStringConcatenation behaves differently with ParserEngine: parser_prism #12834

Open
andyw8 opened this issue Apr 11, 2024 · 1 comment
Labels

Comments

@andyw8
Copy link
Contributor

andyw8 commented Apr 11, 2024

Expected behavior

I'm not sure 100% sure what the correct behaviour is.

Actual behavior

Given this code:

<<~MESSAGE
  \n
  a
MESSAGE

The regular parser allows it, but with parser_prism it fails with:

Combine and "a\n" into a single string literal, rather than using implicit string concatenation.

RuboCop version

1.63.1 (using Prism 0.24.0, rubocop-ast 1.31.2, running on ruby 3.3.0) [x86_64-linux]
  - rubocop-graphql 1.5.1
  - rubocop-minitest 0.35.0
  - rubocop-performance 1.21.0
  - rubocop-rails 2.24.1
  - rubocop-sorbet 0.8.1
@andyw8
Copy link
Contributor Author

andyw8 commented Apr 11, 2024

Possibly related: ruby/prism#2668

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

No branches or pull requests

2 participants