fix(extensions/#2481): Fix blockers for vscode-spell-checker #2509
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
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.
There currently isn't a good spell-check solution for Onivim - the Vim spellcheck dictionaries are not currently integrated, and the vscode-spell-checker extension is blocked by a bug:
This fixes the blocking bug by implementing the missing
$getLanguagesAPI, which the code-spell-checker extension requires. In addition, we were treating all diagnostics as error-level severity in rendering, but spelling should come through as a lower severity - so this wires up the severity type to match the extension host's concept.With this, the vscode-spell-checker extension works, and shows spell-checks alongside compilation errors:
Related to #2481