You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see SuppressWarningsSubProcessor_suppress_warnings_label in org.eclipse.jdt.ls.core/src/org/eclipse/jdt/ls/core/internal/corrections/CorrectionMessages.java, but no such action is offered by getCodeActionOptions in org.eclipse.jdt.ls.core/src/org/eclipse/jdt/ls/core/internal/handlers/JDTLanguageServer.java. Is adding @SuppressWarnings("unchecked") out of vogue or deperecated? How do I deal with this if I want to suppress warnings on a case by case basis, and not session wide?
The text was updated successfully, but these errors were encountered:
We would probably just need to migrate SuppressWarningsSubProcessor from jdt.ui to jdt.core.manipulation and we'd be able to use that. It looks pretty straightforward to do though.
We would probably just need to migrate SuppressWarningsSubProcessor from jdt.ui to jdt.core.manipulation and we'd be able to use that. It looks pretty straightforward to do though.
This is looking extremely possible now due to eclipse-jdt/eclipse.jdt.ui#815 . We should be able to use the classes directly once we update the target platform.
As a note, we've discovered that due to #1062 we shouldn't activate the warning & quick-fixes related to Unsupported @SuppressWarnings("...") because a codebase may have parameters that are not known to Eclipse, but are handled by other tools.
I see
SuppressWarningsSubProcessor_suppress_warnings_label
inorg.eclipse.jdt.ls.core/src/org/eclipse/jdt/ls/core/internal/corrections/CorrectionMessages.java
, but no such action is offered bygetCodeActionOptions
inorg.eclipse.jdt.ls.core/src/org/eclipse/jdt/ls/core/internal/handlers/JDTLanguageServer.java
. Is adding@SuppressWarnings("unchecked")
out of vogue or deperecated? How do I deal with this if I want to suppress warnings on a case by case basis, and not session wide?The text was updated successfully, but these errors were encountered: