redhat-developer / redhat-developer/quarkus-ls
Support for .env
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 50
- Forks
- 18
- Avg merge
- 22h 11m
- Merged PRs (30d)
- 3
Description
See https://quarkus.io/guides/config-reference#env-file
- on MP LS side
We should provide completion, validation, etc for .env file. Collected properties from Java sode (ex: quarkus.datasource.name, should be replaced with QUARKUS_DATASOURCE_NAME)
We should validate sntax for property name according to the rules https://github.com/eclipse/microprofile-config/blob/master/spec/src/main/asciidoc/configsources.asciidoc#environment-variables-mapping-rules
- on MP JDT side
Load .env to load it in JDTMicroProfileProject as config source which will be used for validation and hover for @ConfigProperty/name
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 with the linked Quarkus configuration and MicroProfile environment-variable mapping rules, then inspect the MP LS handling of configuration and JDTMicroProfileProject. Define how .env properties are loaded, mapped, completed, and validated on both sides. Done means .env names are syntax-checked and its values support validation and hover for @ConfigProperty/name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100