Syntax highlighting is broken with array syntax
See original GitHub issue[provide a description of the issue]
Environment
- Operating System: linux
- JDK version: 11
- Visual Studio Code version: 1.29.1
- Java extension version: 0.34
Steps To Reproduce
Snippet:
for (int i = 0; i==0;){
}
String[] aaa = new String[] {
String.class.toString(),
"aaaa",
"bbb",
};
for (int i = 0; i==0;){
}
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Visual Studio Code syntax highlighting is not working for ...
The current version (v5.0.20221116) for JavaScript and TypeScript Nightly seems to be breaking the syntax highlighting.
Read more >Syntax Highlighting - Tree-sitter
This document explains how the Tree-sitter syntax highlighting system works, using the command line interface. If you are using tree-sitter-highlight library ( ...
Read more >Is syntax highlighting broken? - Arduino Meta - Stack Exchange
I removed the c++ in the first question, and now the syntax highlighting is working. If it worked before (with the c++ ),...
Read more >Xcode 12.5 and Xcode 13 beta syntax highlighting is ... - Reddit
Xcode 12.5 and Xcode 13 beta syntax highlighting is so broken. Any fixes? Is there a way to fix syntax highlighting? For Xcode...
Read more >Prism
Download. Prism is a lightweight, extensible syntax highlighter, built with modern web standards in mind. It's used in millions of websites, including some ......
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
@nkibbey It has been fixed in upstream, and has been adopted in vscode-insiders. I just tried in latest vscode-insiders, and it worked. So it’s expected to be shipped in the next stable release of vscode.
@Yanpas sorry I did update my previous comment. Your issue is fixed in upcoming 0.61.0, with semantic highlighting turned on: