New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Diagnostic Tag #1161
Support Diagnostic Tag #1161
Conversation
eclipse-lsp4j/lsp4j#362 was merged. And the change to LSP4J is official now. Please proceed with this one. @testforstephen @fbricon @snjeza |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
org.eclipse.jdt.ls.core/src/org/eclipse/jdt/ls/core/internal/handlers/DiagnosticsHandler.java
Outdated
Show resolved
Hide resolved
eclipse-lsp4j/lsp4j#366 was sent to apply the protocol change regarding capabilities. |
The build failure will recover once the change to LSP4J is merged. |
test this please |
...e.jdt.ls.core/src/org/eclipse/jdt/ls/core/internal/handlers/WorkspaceDiagnosticsHandler.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Rome Li <rome.li@microsoft.com>
Signed-off-by: Rome Li <rome.li@microsoft.com>
Signed-off-by: Rome Li <rome.li@microsoft.com>
Signed-off-by: Rome Li <rome.li@microsoft.com>
fe069b1
to
840a5b9
Compare
The build failures do not seem like caused by this PR... #1183 is tracking this. |
test this please |
Thanks @akaroml ! |
Signed-off-by: Rome Li rome.li@microsoft.com
Fix #1162
And it looks like this when it's running: