redhat-developer / redhat-developer/vscode-java
Auto-completion of generic methods sometimes gives nonsense results
Open
Nobody has claimed this yet.
bug
content-assist
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
I just had auto-completing Stream.emp result in Stream<Object>.empty(), whereas it should complete to Stream.empty().
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 Stream.emp completion in the vscode-java extension and trace the Java completion handling; the payload does not name a source file or test. Done means the completion is Stream.empty() rather than Stream<Object>.empty() for this generic method case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100