-
Notifications
You must be signed in to change notification settings - Fork 31
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
Wrong colorization in Yaml files #3
Comments
Thanks for letting me know about the issue. The way VS Code handles languages is different depending on if they are core to the editor or come as an extension. Extensions can't override core languages very easily and have to use hackery sometimes to get things to work. Give me a couple of days to take a look at it to see how to implement the changes. |
To expand a bit on my last comment, see microsoft/vscode#1751 for more information on what I mean. I can't immediately fix this issue without rewriting the YAML syntax from scratch or until Microsoft fixes the language override issue. This will take some time to fix, but I can do it. |
At this point, I don't see myself being able to rewrite the YAML language to make this work and this is technically not a bug with the plugin, but a limitation of Code. As such, there is nothing I can really do about this until I get time or they fix language overrides in Code. I'm closing as Won't Fix for now. |
Ok, I got it. Thank you for your efforts! чт, 10 нояб. 2016 г. в 9:51, William Holroyd [email protected]:
|
Ended up getting blocked on this as it didn't work in YAML for all scenarios, so it's on pause. Linking to #19. |
Could you check following examples? Looks like Jinja colorization works wrong.
Example 1:
Example 2:
Example 3:
The text was updated successfully, but these errors were encountered: