Filter contract symbols from CodeLens - #15
Merged
Conversation
- 🐛 Ignore default exports and properties outside class or interface members - ✅ Cover Hono-like contract keys while preserving class property lenses - 📚 Document conservative symbol matching
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.
Summary
Keeps Zero Reference focused on symbols that static analysis can judge without pretending runtime contracts are dead code 🐛🔍 The classifier now uses document-symbol hierarchy while preserving useful class and interface member hints 😎👍
Motivation
Object payload keys, inline type bindings, and default exports can be consumed by frameworks or external clients without appearing in the VS Code static reference graph. Reporting them as zero-reference symbols creates misleading cleanup hints, while class and interface members remain useful candidates 🎯