feat: Made the LSP typeDeclarationProvider
specify order="last"
to help ensure that it will be invoked after other implementations
#686
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 aslast
(at which point it's just about the plugin loading order).