redhat-developer / redhat-developer/vscode-java
dont collapse imports to .* if it result in ambigous imports
Open
Nobody has claimed this yet.
code action
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
not sure if its always been like this way but these days I keep getting caught by ambiguous imports.
I could raise the limit but could it not fail the collapse i the result is ambiguous imports?
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 by reproducing the ambiguous-import behavior in the VS Code Java extension and locate the logic that collapses imports to a wildcard. Determine how to detect whether the collapsed imports become ambiguous; done when ambiguous imports are not collapsed while the existing import-collapse behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100