feat: add Code Lens "N references" for Flex abbreviations (closes #39)#42
Merged
Conversation
This file contains hidden or 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
1 participant
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.
Type of change
What does this PR do?
Adds "N references" Code Lens entries for Flex abbreviation definitions,
consistent with the existing Code Lens for start conditions and Bison rules.
Each abbreviation declared in the definitions section now shows a clickable
"N references" lens that opens the References panel pointing to every
{ABBR}usage in the rules section (including transitive usages recordedsince v1.5.2).
Related issue
Closes #39
How to test manually
.lfile with abbreviation definitions → each abbreviation lineshows "N references" above it.
{ABBR}occurrences.Checklist
npm run compilepasses with no new errors