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
Currently, the extension automatically detects strings starting with certain words as sql syntax but this wouldn't work if the string first starts with tabs, spaces, and line breaks and then has those words. It'd be great if it could skip whitespace characters and check the first valid word for syntax highlighting.
The text was updated successfully, but these errors were encountered:
I ran into the issue with WITH today as well, and would love it if that were on the list of SQL-start keywords. This also matches up nicely with the recently-submitted issue #109, regarding whitespace at the beginning of the string before a magic keyword. We regularly put a large inline query at the start of the next line, so having whitespace be ignored (and recognizing WITH) would save us a whole lot of --sql sprinkled everywhere.
Currently, the extension automatically detects strings starting with certain words as sql syntax but this wouldn't work if the string first starts with tabs, spaces, and line breaks and then has those words. It'd be great if it could skip whitespace characters and check the first valid word for syntax highlighting.
The text was updated successfully, but these errors were encountered: