[ 
https://issues.apache.org/jira/browse/CAMEL-23874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-23874:
--------------------------------
    Fix Version/s: 4.22.0

> DevConsole - add option metadata so consoles can declare supported options
> --------------------------------------------------------------------------
>
>                 Key: CAMEL-23874
>                 URL: https://issues.apache.org/jira/browse/CAMEL-23874
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 4.22.0
>
>
> Currently dev console options are passed as a free-form Map<String, Object> 
> and each console parses them ad-hoc with optionString/optionInt/optionLong 
> helpers. There is no way for tooling (CLI, TUI, MCP, JSON metadata) to 
> discover what options a console supports, their types, defaults, or 
> descriptions.
> Add a formal mechanism (e.g. annotation or method) for dev consoles to 
> declare their supported options with metadata: name, type, default value, 
> description. This would allow the JSON catalog/metadata to expose available 
> options per console, enabling better tooling support and discoverability.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to