redhat-developer / redhat-developer/vscode-quarkus

Warn of properties being overridden in property files

Open
#192 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
79
Forks
31
Avg merge
12h 51m
Merged PRs (30d)
6

Description

Per the 3rd bullet in the comment on issue 181, an additional nice feature would be yellow underlining of properties that are being overridden (or are overriding) the same property from another config source. For example, if quarkus.http.port is in both the microprofile-config.properties and application.properties, then the yellow underline message in microprofile-config.properties should be that it is being overridden by application.properties, and in application.properties, there should be a message that it is overriding the same property in microprofile-config.properties.

It would be nice to take this to the "next level", notifying of duplicate properties defined in system properties ("-D"), environmental variables, and application.yaml as well.

This requirement does not include custom or dynamic config sources, although that would admittedly be a nice touch.

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 with the third bullet in the comment on issue 181, then locate the extension entry point that validates or underlines configuration properties. Define completion as diagnostics for duplicate properties across microprofile-config.properties, application.properties, system properties, environment variables, and application.yaml, while excluding custom or dynamic sources.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.