Re-write extension to use reactive-vscode, align with Vue extension #790
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.
The Vue extension which runs atop Volar still has a number of tricks (hacks?) to get typed Vue in TS Plugin mode (aka hybrid mode) working properly. It'll be easier to follow along with these hacks if our extension has as similar a structure as possible.
To that end I've followed along with the Vue extension's refactor to use reactive-vscode.
reactive-vscodeuses Vue's composition API (similar to starbeam signals/computeds/etc) to provide a more user-friendly reactive layer over the more observer-centric VSCode extension API. It's a nice set of primitives on its on but more importantly this lets us follow Vue's extension logic/hackery more closely.