Allow retrieving a tree's list of included ranges, fix some included range bugs #1952
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
Co-authored-by: Nathan Sobo <nathan@zed.dev>
Previously, when an included range started or ended *inside* of an edit, that range did not get updated correctly. Co-authored-by: Mikayla Maki <mikayla@zed.dev>
maxbrunsfeld
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.
Closes #1939
This PR adds a
ts_tree_included_rangesfunction to the C API, which allows you to retrieve the included ranges that were used to parse a tree.I've also fixed some other bugs related to the
included_rangesAPIs:ts_tree_get_changed_ranges.included_rangein certain circumstances, leading to false parse errors.included_range, which could lead to infinite loops in certain cases.