feat: TextDocument and incremental sync helper #5
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
wkillerud
force-pushed
the
text-documents
branch
from
4d90c19 to
997b721
Compare
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.
Hello 👋 Sorry for cold-opening such a large addition 😅 Hope it's of interest, and I'm definitely open for feedback.
This PR adds support for incremental document sync and a
TextDocumentAPI that matches vscode-languageserver-textdocument.Following up on #4, this is the second part of the Node API I felt was missing. Having
TextDocumentespecially is going to make life easier formefolks looking to migrate from Node to Dart, or who use VS Code examples as reference.