[
https://issues.apache.org/jira/browse/CAMEL-22205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18013869#comment-18013869
]
Claus Ibsen commented on CAMEL-22205:
-------------------------------------
Aurelien, it would be good to add a ticket to the vs-code plugin / LSP so we
can have support for this tool to understand completions for camel.jbang.xxx as
well.
Then this can also work with the camel-jbang edit command from CLI and as well
in VSCode and Kaoto etc.
> Provide Camel JBang properties in Camel catalog
> -----------------------------------------------
>
> Key: CAMEL-22205
> URL: https://issues.apache.org/jira/browse/CAMEL-22205
> Project: Camel
> Issue Type: New Feature
> Components: camel-catalog, camel-jbang
> Reporter: Aurélien Pupier
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.14.0
>
>
> Camel Jbang is leveraging several specific properties inside
> applications*.properties
> For instance for the export:
> https://camel.apache.org/manual/camel-jbang.html#_configuring_exporting
> Having them in the Camel catalog will allow to provide completion/validation
> to this file in various tooling.
> Given that initial purpose of applications.properties was not targeting
> end-users, not sure we should push in this direction.
> Note that dependign on the command, the list of parameters used may vary.
> Maybe the "group/tag/label" can be used to specify that
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
