You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the issue
In a .js file when having a string literal that includes '/*' , it thinks you're trying to start a multiline comment. This messes up syntax highlighting for that lines and the lines after it.
It happened to me when I wanted to have a wildcard selector for path names as you see in the screenshots below.
Screenshot of Current Behavior
Screenshot of Expected Behavior
Workarounds
The issue only happens when using string literals, if you separate the string like this, the issue goes away.
The text was updated successfully, but these errors were encountered:
Describe the issue
In a .js file when having a string literal that includes '/*' , it thinks you're trying to start a multiline comment. This messes up syntax highlighting for that lines and the lines after it.
It happened to me when I wanted to have a wildcard selector for path names as you see in the screenshots below.
Screenshot of Current Behavior
Screenshot of Expected Behavior
Workarounds
The issue only happens when using string literals, if you separate the string like this, the issue goes away.
The text was updated successfully, but these errors were encountered: