microsoft / microsoft/vscode-java-dependency
UX improvement for adding external JARs
@jdneo is already working on this.
Since Dec 23, 2021.
- Dominant language
- TypeScript
- Stars
- 199
- Forks
- 105
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 27
Description
Per survey user feedback, it seems the way to add external JARs is sometimes not obvious or straightforward to the users, especially users who come from IDE background, so creating this issue for discussion
Original words:
“No intuitive way to add external JARs. Just learning Java and had to install Eclipse to figure it out”
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
The issue concerns the external-JAR workflow in this VS Code Java extension, but names no files, tests, or entry points. First inspect how users currently add external JARs and review the discussion context; done would be a more intuitive workflow for users coming from IDEs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100