redhat-developer / redhat-developer/vscode-java
Provide an editor to open the diagnostics at project level
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
Currently when you click an error at project root level in PROBLEMS view, it will throw some error saying Unable to open 'project': File is a directory.
This error is like a bug. When the problems are showed in the PROBLEMS view, the user will expect to open the resource and able to fix it. For the Java language server, the closest project configuration resource file is .classpath, however it's apparently not friendly for user to edit it manually. One idea is the Java language server provides a special web view to show the project structure (such as build path).
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 project-root error from the PROBLEMS view and tracing how the Java language server handles that diagnostic. Review the project configuration represented by .classpath and determine the scope of the proposed project editor or web view. Done means clicking a project-level diagnostic opens a user-friendly resource that supports fixing the problem without manually editing .classpath.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100