Add enclosing_range to Occurrence message
#150
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
olafurpg
requested changes
May 3, 2023
olafurpg
approved these changes
May 3, 2023
|
A good followup PR would be to add |
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 PR adds a field to
Occurrencewhich we plan to populate as a by-product of symbol generation or highlighting. We will consume this almost immediately in the Cody context APIs to break off only the relevant portion of a code intelligence result. This will also allow us to generate more intelligent embeddings chunks. This can also help us determine call hierarchies as we now have a way to extract symbols within the implementation of a given symbol (by range).Test plan
N/A