eclipse-wildwebdeveloper / eclipse-wildwebdeveloper/wildwebdeveloper
Autocompletion on js files does not consider context
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 201
- Forks
- 76
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 21
Description
The autocompletion always seems to offer standard classes and keywords not considering text left to the cursor, resulting in hundrets of - in my opinion - useless proposals
In the example I would expect some result filtering. Ex selecting the entry 'yield' results in "myield" in the editor, which is totally useless.
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 using the attached JavaScript autocompletion example and inspect the project's JavaScript completion path. Confirm how text before the cursor affects proposals and verify that selecting yield no longer produces myield; the issue is done when irrelevant proposals are filtered by context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100