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
As you can see, the backslash-escaped double-quote is where the syntax highlighting breaks. I assume it's because the regex is expecting a closing double-quote, instead of treating it as a literal character.
This screenshot shows how the syntax highlighting should work, because this code example uses the Progress-suggested way of escaping. But, the documentation also allows for Unix-style escaping with a backslash, and so it would be excellent if this extension could be updated to allow the backslash as an escape character, too.
Thanks!
The text was updated successfully, but these errors were encountered:
As you can see, the backslash-escaped double-quote is where the syntax highlighting breaks. I assume it's because the regex is expecting a closing double-quote, instead of treating it as a literal character.
This screenshot shows how the syntax highlighting should work, because this code example uses the Progress-suggested way of escaping. But, the documentation also allows for Unix-style escaping with a backslash, and so it would be excellent if this extension could be updated to allow the backslash as an escape character, too.
Thanks!
The text was updated successfully, but these errors were encountered: