-
-
Notifications
You must be signed in to change notification settings - Fork 32
add support for stTheme #59
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
Conversation
also changed xml scope for better&faster read of colors + support
something like (<string><![CDATA[ html { position: relative; color:
#A83B40; } ]]></string>)
| "syntax_files": [], | ||
| "syntax_filter": "whitelist", | ||
| "base_scopes": ["text.xml"], | ||
| "scan_scopes": ["text.xml -meta.tag.xml -comment -string"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not okay with this change. Why not do something like this?
"scan_scopes": ["text.xml -meta.tag.xml -comment -string, string.unquoted.cdata.xml"],
|
because its not future proof, it means that with every time something new comes out u will have to update the settings. |
Very little in this world is.
I don't think the XML language changes very much and nor does the color schemes, and we never want to search comments. CDATA makes sense in the context of color schemes which is why I am okay with it. Comments and XML attribute strings don't. |
|
In my defense though, a setting file that can be easily updated when changes are needed does kind of make it future proof 😉 . It's all relative to the angle you are viewing it from. |
|
okay than. |
|
Is there a reason the issue got closed and not updated? I have no problems adding |
|
aaaaaa,okay ,my bad |
|
I was just reviewing the code, wasn't trying to shut this down 😉. |
|
point taken 👍 |
|
I just went ahead and manually merged what I wanted. |
also changed xml scope for better&faster read of colors + support
something like