-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alternative quoting mechanism (''q'') for string literals is breaking symbol recognition and syntax highlighting #81
Comments
This feature is not supported yet. |
Hi, thank you. This feature is used very often these days - in dynamic SQL, templates and also in simple strings to avoid the escape hell by double, triple or even more single quotes. The readability and maintainability of code is much better with it. For me (and may be for many others) it is essential to support this. If I can help you please let me know - at least for testing or may be also for coding. Kind regards |
If you know well regexp, you can always make a PR, to help me to implement such a feature. |
Hi, I am totally new to extension development for VS Code. Anyway, I will try it. You will here from me - either with questions or a solution. Best regards |
You have 2 sources to adapt:
|
Hi, thanks for the infos. I will definitly try it and come back to you. Please do not wonder when it takes a little bit longer (have to finish some things before on my own projects). You will hear from me... Best regards |
I am having the same issue and I have the most recent version. Just wondering how do I modify/find plsql.tmLanguage? |
Problem is actual. Extension does not support Alternative Quoting Mechanism (''Q'') for String Literals |
Hi again,
when using alternative quoting the symbol recognition is broken and the syntax highlighting is also not working correct.
For a description of the feature please see this Live SQL example from Steven Feuerstein.
Following a code example which is working in SQL Developer without problems (see screenshots below).
Thank you in advance and kind regards
Ottmar
The text was updated successfully, but these errors were encountered: