Syntax highlighting breaks if there is a linebreak between "styled" and opening backtick `
See original GitHub issueSee the screenshot, once there is a linebreak between styled
and the opening backtick `
CSS syntax highlighting stops working. A normal use case for this would be e.g. declaring an anonymous interface for props
in Typescript that spans multiple lines.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:19
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Syntax highlighting is broken when you don't specify a ...
Syntax highlighting is broken when you don't specify a language explicitly ... Shouldn't it be able to autodetect common or known languages?
Read more >Add syntax highlighting and line breaks to comment formatting
There is no ability to post new lines in a comment. I would suspect that this is because it is a general idea...
Read more >Add syntax highlighting to your Jekyll site with Rouge - BNHR
Case 1: If you won't put a linebreak between the list item and the code-block, have the code-block aligned with the indentation of...
Read more >Features for Coders - Marked 2
Fenced Code Blocks; Syntax Highlighting; GitHub Linebreaks ... some minor rendering differences between it and colorizers such as Pygments (GitHub style), ...
Read more >5.6 Verbatim code chunks | R Markdown Cookbook - Bookdown
The verbatim content will be syntax highlighted using the markdown language in ... two consecutive line breaks means starting a new paragraph); (2)...
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
This has been fixed in v1.5.1 please let us know or raise an issue if this is still happening
Hey @rkingon, thanks for finding this. I think https://github.com/styled-components/vscode-styled-components/issues/169 is the same issue which should address that