redhat-developer / redhat-developer/vscode-quarkus
Certain commands may result in @ConfigProperty name keys marked as unused when declared in property file
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 79
- Forks
- 31
- Avg merge
- 12h 51m
- Merged PRs (30d)
- 6
Description
When I use https://github.com/quarkusio/quarkus-quickstarts/tree/main/config-quickstart , if I call the command to clean the Java language server workspace, or add an extension to the current project it loads and I see a warning on greeting.message (and also greeting.name) that
The property 'greeting.message' is not assigned a value in any config file, and must be assigned at runtime.microprofile-config(NO_VALUE_ASSIGNED_TO_PROPERTY)
despite the fact that https://github.com/quarkusio/quarkus-quickstarts/blob/496cb69159c59fad207c6bd8b82e4a4667dffc09/config-quickstart/src/main/resources/application.properties continues to contain the relevant properties.
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
Reproduce with the config-quickstart after cleaning the Java language server workspace or adding an extension. Inspect GreetingResource.java and config-quickstart/src/main/resources/application.properties, then trace how the extension reads the declared properties. Done means greeting.message and greeting.name no longer show NO_VALUE_ASSIGNED_TO_PROPERTY when those properties remain in the file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100