camel-tooling / camel-tooling/camel-language-server

Support Quarkus profiles in application.properties

Open
#1,361 0 comments 0 reactions 0 assignees View on GitHub
IMPROVEMENT
Dominant language
Java
Stars
56
Forks
26
PR merge metrics
No merged PRs in 30d

Description

we can use Quarkus profiles for the properties in the application.properties. In this case, the Camel properties are still valid but the language server is not handling it.

for instance:
%prod.camel.component.kafka.brokers=xxx
%dev.camel.component.kafka.brokers=yyy

it would be nice to have the camel completion and validation and after %XXX.camel.

Contributor guide

Open the contributing guide

Research direction

Start by locating the application.properties parsing, completion, and validation entry points in the language server. Add coverage for the %prod and %dev profile examples, then verify that Camel completion and validation work after the profile prefix.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.