redhat-developer / redhat-developer/vscode-java
Signature Help focuses on wrong signature
Open
Nobody has claimed this yet.
bug
content-assist
signature help
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
Tested with the v1.20.2023061504 pre-release, given a JUnit assertion:
assertEquals("one", "two");
Typing , after "two" will propose the wrong signature:
an assertion on Strings should be selected
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
Reproduce the issue in VS Code using the v1.20.2023061504 pre-release and the JUnit assertion shown in the report. Check Signature Help after typing the comma; done means the String assertion signature is selected instead of the wrong overload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100