forked from ptweir/python-string-sql
-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Description
Example code:
<?php
/**
Query to be executed.
*/
$query = "
set search_path = '%SCHEMA%';
";
// test
function abc() {
return "test";
}Steps/problems
Once I type in "SELECT" the string becomes unterminated and brakes whole file basically:

Another example of broken highlighting because a comment happen to have "SELECT" in upper case:

Another example where both SELECT and --being-sql is used. Notice how function is not highlighted:

Expected
- I guess this auto-open, even in comments, is something some one would want, but it brakes my code. Would be great to be able to disable it in settings.
- Auto-open (with uppercase keywords) should only be triggered within strings (at least by default).
- String termination should terminate the highlighter (would also probably solve
--beginsql, --endsql"""doesn't terminate highlighting #19). - If you want to support SQL in comments then comment termination should also terminate the highlighter. That should be optional.
- When
--begin-sqlis used auto-open should not be used.
Metadata
Metadata
Assignees
Labels
No labels
