-
Notifications
You must be signed in to change notification settings - Fork 417
Avoid retrieving AST root during diagnostic publishing. #2574
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
Conversation
....jdt.ls.core/src/org/eclipse/jdt/ls/core/internal/handlers/BaseDocumentLifeCycleHandler.java
Outdated
Show resolved
Hide resolved
I can confirm the the vsix reduces the time to publish diagnostics from a few seconds to a few hundred ms with the vsix. However, this doesn't happn when I build and run against the PR. I even tried with the exact same settings. I think the change is fine to merge, but why the difference ? Update: Also please rename the commit title to something like |
Remove CoreASTProvider.getAST(...) from BaseDocumentLifeCycleHandler.publishDiagnostics(IProgressMonitor) - eclipse-jdtls#2535 Signed-off-by: Snjezana Peco <[email protected]>
Fixed |
17.1.3 vsix also includes #2535 |
I think I was rebasing your patch to be on top of the latest commit. Even now I'm seeing validation take a few seconds whereas with your vsix it's a few hundred ms. Update: I'll merge, but it would be good to verify why I'm seeing this. |
Did you enabled lombok? |
A related issue - redhat-developer/vscode-java#2982
Steps to reproduce
Validated X. Took XXX ms
Test vsix 1.17.3