JS Custom last update break syntax highlighing
See original GitHub issueHi, i upgrade JSCustom to the latest version 2.3.1 this morning and i face an issue with syntax highlighting
I get all my jsx to get no highlight :
and i get it back when i comment the section with||
operator
I have no idea where it come from but i get this on all my files. ( For example i have a switch case where only the first case is highlight)
Have you any idea where does it come from ?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
TypeScript / JavaScript syntax highlighting changes after a few ...
I just updated and my javascript syntax highlighting broke. VSCode Version: 1.43; OS Version: Windows 10. Does this issue occur when all ...
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 >Upgrading to Highlight.js v11.0
Welcome to version 11.0. This a major release and therefore contains breaking changes. Below is a complete list of those such changes. Built-in...
Read more >Adding syntax highlighting | Customization - Zenplates
The highlight.js library is a quick and easy way to automatically add syntax highlighting to your code examples, based on a dynamically detected...
Read more >What's wrong with this CSS code so syntax highlighting seems ...
The following CSS snippet in a Stack Overflow snippet currently seems to have broken syntax highlighting. .grid_body { display: grid; grid- ...
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 Free
Top 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
v2.3.2 is out, and it should fix this. Upstream changes to object literals broke the
string_object_keys
extension, and the tests didn’t catch it because… there aren’t any tests forstring_object_keys
. I’ll write some for the next release.Please reopen the issue and post a comment if the problem recurs in v2.3.2.
Thanks everyone for the prompt reports and for identifying
string_object_keys
as the culprit — it would have been a lot harder to track down otherwise, especially because I don’t usestring_object_keys
myself.This started today for me, too. It’s happening when I have
string_object_keys: true