Option to disable highlighting of TODO comments
See original GitHub issueWhen I put a TODO in a comment in a Java file, the Java extension highlights it with a squiggly underline. As I have a dedicated todo-highlighter extension which suits my needs far better, I’d like to disable the underlining of these comments. I’ve looked, but I can’t find anything in the settings to disable this. Could a setting for it be added?
Environment
- Operating System: Windows 10
- JDK version: 11.0.12
- Visual Studio Code version: 1.60.2
- Java extension version: 0.82.0
Steps To Reproduce
- Add a comment in a Java file, such as
// TODO: Somethingor// FIXME: Something else - Observe that a blue underline appears on the comment.
Current Result
See above
Expected Result
See above
Additional Informations
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
highlight - Turn off syntax hilighting for TODO items
Another option: Since TODOs are often in comments, if you want the TODO to end up having the same highlighting as regular comments, ......
Read more >vscode-todo-highlight - Visual Studio Marketplace
Highlight TODO , FIXME and other annotations within your code. ... You can override the look by customizing the setting.
Read more >TODO comments | IntelliJ IDEA Documentation - JetBrains
IntelliJ IDEA lets you add special types of comments that are highlighted in the editor, indexed, and listed in the TODO tool window....
Read more >How do I disable "TODO" warnings in pylint? - Stack Overflow
In pylint.cfg, I can disable checker W0511, which is the checker that complains about "TODO" and similar terms in comments.
Read more >Option to disable built in keywords · Issue #83 · wayou/vscode ...
Having no way to remove the built in highlighting for TODO: and FIXME: is problematic for me. ... akbyrd opened this issue on...
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

Agreed. If we can figure out that the property accepts a set of values (as opposed to enabled/disabled), then we can certainly define our “Ignore this option” code action to set it empty.
Given that there is a workaround, and that we’ll make progress on this in https://github.com/eclipse/eclipse.jdt.ls/pull/1765 , I’ll mark this as a duplicate.