redhat-developer / redhat-developer/vscode-quarkus
Expose API / command to get all quarkus properties as k/v pairs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 79
- Forks
- 31
- Avg merge
- 12h 51m
- Merged PRs (30d)
- 6
Description
In a JBang file with quarkus dependencies, we can use the //Q:CONFIG directive to configure the application
From jbang-vscode, I'd like to be able to fetch the list of available key/value pairs by calling a vscode-quarkus command (as a follow up of https://github.com/jbangdev/jbang-vscode/pull/102).
The "project" not being a Maven/Gradle project might be an issue. Hopefully not. We just need to find the properties from the underlying project's classpath.
I imagine the command would just need the file URI as a parameter. From there it should be able to find the Java project it belongs to, then collect all dependencies from the classpath. Getting deployment jars when it's neither a maven or gradle project might be tricky.
Anyways, nothing urgent, really a nice to have.
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 reading the jbang-vscode follow-up in pull request #102 and the existing vscode-quarkus command integration. Investigate how a JBang file URI can identify its Java project and classpath, including deployment jars outside Maven or Gradle. Done means exposing a command that accepts the file URI and returns all available Quarkus configuration key/value pairs.
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
- Mostly clear
- Newbie friendliness
- 25/100