fix(ruby): scope string overrides to literal content - #319
Merged
Conversation
The Ruby extension currently applies the string scope to the entire string node. This includes Ruby interpolation expressions. Limit the scope to string content instead. Keep interpolation expressions in the normal Ruby scope. This keeps string-specific settings, such as Tailwind language-server opt-in and completion query characters, inside literal string content. Closes #313
vitallium
force-pushed
the
vs/fix-interpolation-completion
branch
from
August 29, 2026 20:36
59a1b33 to
ff9a706
Compare
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
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.
The Ruby extension currently captures each entire string with:
A Ruby string can contain executable Ruby code:
"The result is #{user.name}"The broad capture also applies the string scope to
user.nameinside the interpolation. This can enable string-specific settings in normal Ruby code.Changing the query to:
fixes the problem.
This limits the string scope to literal content:
This keeps string-specific settings, including Tailwind language-server opt-in and completion query characters, inside Ruby string content. Ruby code inside
#{...}keeps normal Ruby behavior.Closes #313