Skip to content
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

feat: Made the LSP typeDeclarationProvider specify order="last" to help ensure that it will be invoked after other implementations #686

Merged

Conversation

SCWells72
Copy link
Contributor

Testing with a local pre-release build of LSP4IJ, I noticed that it was interfering with the same EP implementation in another language, and debugging a bit, I could see that LSP4IJ's was slotted in before that other one. By explicitly specifying order="last", it is guaranteed to execute after all other EPs that don't also register themselves as last (at which point it's just about the plugin loading order).

…ure that it will be invoked after other implementations.
@SCWells72 SCWells72 changed the title feat: Made the LSP typeDeclarationProvider specify order="last" to help ensure that it will be invoked after other implementations feat: Made the LSP typeDeclarationProvider specify order="last" to help ensure that it will be invoked after other implementations Dec 11, 2024
@angelozerr angelozerr merged commit 5157bd2 into redhat-developer:main Dec 11, 2024
7 checks passed
@angelozerr
Copy link
Contributor

Thanks

@angelozerr angelozerr added the bug Something isn't working label Dec 11, 2024
@angelozerr angelozerr added this to the 0.9.0 milestone Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants