-
Notifications
You must be signed in to change notification settings - Fork 443
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
Return the API before importing the projects #2905
Return the API before importing the projects #2905
Conversation
3e25759
to
ccb426c
Compare
ccb426c
to
5b52f36
Compare
Yup, the underlying issue here was definitely a startup issue. Wouldn't be surprised if we hit it now because VS Code started properly waiting for extension activation. The early |
761a9a2
to
b8162c2
Compare
This also has the side effect that extensions that depend on vscode-java can start up sooner. Fixes redhat-developer#2900 Signed-off-by: David Thompson <davthomp@redhat.com>
b8162c2
to
f7d75e7
Compare
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.
Change works for me.
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.
LGTM.
Though the API instance is resolved early, plugins of JDT-LS can leverage and wait serverReady()
during activation.
@jdneo I'll merge this. I would just keep an eye on any extension tests that may depend on this, or any places that make any assumptions about the state of the language server through the api manager immediately on startup. |
This also has the side effect that extensions that depend on vscode-java can start up sooner.
Fixes #2900
Signed-off-by: David Thompson davthomp@redhat.com