Command: Generate CodeLenses using Tree-Sitter query #3861
+33
−51
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.
Refactor code lens generation for Cody Commands.
Updated to use tree-sitter for documentable nodes to display code lenses more accurately, instead of counting on folding ranges. This helps with the issues where code lenses are showing up in non-documentable nodes
Test plan
Enable Code Lenses in Cody to check if the lenses are showing up.
Before
Code Lenses are showing up randomly due to folding ranges positions in large functions or classes:
After
Code Lenses will not show up in non-top-level-documentable nodes:
Known limitation: documentable nodes do not work with arrow functions