Fix issue with registerContributor API #177
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JPinkney
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a WIP PR that seeks to fix the issues with the registerContributor API. As far as I can see the only way we can trigger https://github.com/redhat-developer/yaml-language-server/blob/master/src/languageservice/services/schemaRequestHandler.ts#L68 from inside of the json language service is to call jsonLanguageService.configure() before we actually handle the hover and validation requests.
Hover and validation are the only requests that would need this as auto completion still uses code inside of the project, rather than delegating to the json language service, and document symbols does not need a schema.