redhat-developer / redhat-developer/vscode-java
Feature Request: Add option to not include references import statements
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
When using the Java Code Lens, or finding references to a class, import statements are included as references. While these are technically references to the class, they are rarely useful and are just added noise to what I'm really interested in, which is where the class is actually being used. It would be nice to have an option to be filter out import statement references.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Java Code Lens and find-references behavior described in the issue, then trace where import statements are included as references and how options are exposed. Done means users can choose to exclude import references while normal reference results remain available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- developer-experience, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100