redhat-developer / redhat-developer/vscode-java

Make project import interactive

Open
#4,156 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement import
Dominant language
TypeScript
Stars
2.3k
Forks
546
Avg merge
20h 1m
Merged PRs (30d)
11

Description

Right now, importing Java projects is happening at startup. I am aware that there is the "interactive" mode, but all that allows me to do is to veto the import of the projects. (If I select "later", how do I later import the projects? There seems to be no "Import Projects" command 🤷 )

Let's consider making the import more interactive by

  • allow the user to pick which directories will be imported
  • allow the user to select which import will import a directory is two or more want to import a given directory
  • allow importers to ask the user to fix problems while importing (think "no compatible Java version" could be fixed by selecting a JDK directory).

In order to implement something like this, we'd have to move control of the import process to the vscode-java side instead of handling import in the language server. That would also alllow us to give more precise feedback if something goes wrong with the import. IMO.

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 tracing the startup import flow, the existing interactive mode, and the boundary between the VS Code extension and language server. Define how users choose directories and importers, resolve importer problems, and later trigger imports; done means these interactions provide precise feedback without relying on startup-only importing.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.