Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Ignore unknown @SuppressWarnings
See original GitHub issueI have project that has a lot of @SuppressWarnings annotations for pmd and checkstyle. The eclipse parser however does not know about these extra warning names, and because of this intellisense has a warning on every usage. This is a bug in the backing language server, but however the recommendation for years has been to disable all Unhandled Token warnings in eclipse. However, I can’t find a way to set that from the vscode extension. I don’t expect the actual backing issue fixed in here, but being able to disable that warning would be really helpful.
https://stackoverflow.com/questions/5017569/unsupported-suppresswarningspmd-donotcallsystemexit
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:8
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
“Unsupported SuppressWarning” warnings are now ignored by default. To get a different behaviour, one needs to set org.eclipse.jdt.core.compiler.problem.unhandledWarningToken=ignore|warning|info|error
We’ve been getting more and more complaints about this specific warning from our users. It seems kind of backwards that a warning specifically designed to suppress warnings is actually causing more warnings. I feel like that warning specifically should be silenced by default, because otherwise its backwards from what it actually is designed to do.