fix: multi-line import expression syntax highlighting #16
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.
Changes Made
begin
regular expression inimport-expression
by removing the end-of-line anchor ($
). This allows the expression to match the opening{
even if it's not on the same line as the@
symbol.end
regular expression inimport-expression
by removing the start-of-line anchor (^
), whitespace matcher (\\s*
), and the end-of-line anchor ($
). This modification allows the expression to match the closing}
regardless of its position on the line.Testing
The fix has been tested with various single-line and multi-line import expressions to ensure syntax highlighting doesn't break later in the file. I might not be familiar with all use cases, so I'd recommend checking any expected patterns.