Syntax highlighting for '@import' rules is broken
See original GitHub issueHi, not sure if this issue is related to [this] but it appears that the colouring is now broken for injectGlobal
It seems fine with normal components however:
Thanks for this really nice extension [this]: https://github.com/styled-components/vscode-styled-components/issues/50
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Syntax highlight is broken when changing the view state - v6
Hello, I'm building a simple code editor in browser with file tree support. so basically I've a single dom element (BTW I'm using...
Read more >Syntax Highlight Guide | Visual Studio Code Extension API
A guide to syntax highlighting. ... The tokenization of text is about breaking the text into segments and to classify each segment with...
Read more >Syntax highlighting not working for Python in VS Code with ...
I'm using "python.formatting.provider": "black" but I also tried autopep8 and yapf . They all seem to fail in the same way, by getting...
Read more >Known failures - Prism.js
Known failures. A list of rare edge cases where Prism highlights code incorrectly. ... There are always such cases in every regex-based syntax...
Read more >ESLint | IntelliJ IDEA Documentation - JetBrains
See Configuring ESLint highlighting to learn how to override these settings. ... You can import some of the ESLint code style rules to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think you would have to use
const importUrl = '\'https://fonts.googleapis.com/css?family=Open+Sans|Roboto\'';
I don’t think it should be the recommended way, but it works for now.
Oops. I forgot
@import
rules are valid ininjectGlobal
. I will try to fix that later today.