microsoft / microsoft/vscode-java-dependency

Combined Classpath View

Open
#706 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
199
Forks
105
Avg merge
1d 22h
Merged PRs (30d)
27

Description

Is it possible to change the view so that it just shows the classpath and ignores all other files? I dislike the separation between src/test/** and src/main/** and feel like that should be within a single view. Any thoughts or ways I can do this? This is true with both the "flat view" and the "hierarchical view" as well.

Environment
  • Operating System: Windows 10
  • JDK version: OpenJDK 11
  • Visual Studio Code version:
    image
  • Java extension version:
  • v1.14.2022120603
  • vscode-java-dependency viewer version
  • v0.21.2022111900
Steps To Reproduce
  1. Step 1 Create a fresh project using https://start.spring.io underneath create files/folder(s) under the following path src/test/java/**.java this pattern follows the standard conventions around maven.
  2. Open project with VSCode

[Please attach a sample project reproducing the error]
Please attach logs

Current Result

image

Expected Result

image

Additional Informations

Dupe of https://github.com/redhat-developer/vscode-java/issues/2829 bc I was dumb and opened it on the wrong repo.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked duplicate, redhat-developer/vscode-java issue 2829, and compare the dependency viewer's flat and hierarchical views in a sample Maven project. Done means the classpath can be presented as one combined view without the current src/test and src/main separation, with behavior defined for the other files shown today.

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
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.