[
https://issues.apache.org/jira/browse/CAMEL-17097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17430472#comment-17430472
]
Claus Ibsen commented on CAMEL-17097:
-------------------------------------
Yeah for EIPs we should maybe use same case as we do for XML, eg what they are
named in the model definition classes.
So that means CamelCased, eg wireTap and so on. Then the DSL examples are more
similar.
The parameters, can however be in mixed style as it uses the property binding
support in camel-core that accepts all kind of styles.
> YAML DSL Camel Case
> -------------------
>
> Key: CAMEL-17097
> URL: https://issues.apache.org/jira/browse/CAMEL-17097
> Project: Camel
> Issue Type: Improvement
> Reporter: Marat Gubaidullin
> Priority: Major
>
> 1. YAML DSL uses Camel Case for Component parameters, ex *authorizationToken*
> {code:java}
> - from:
> uri: "timer://tick"
> parameters:
> period: "1s"
> steps:
> - to:
> uri: "telegram:bots"
> parameters:
> authorizationToken: "XXX"
> {code}
>
> 2. YAML DSL uses Kebab Case for EIP and EIP parameters, ex:
> [do-catch|https://github.com/apache/camel/blob/eb4b84ad37d7e1e94165dcb966f7ed1d8114f508/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/camel-yaml-dsl.json#L17],
> *wire-tap*,
> [parameters|https://github.com/apache/camel/blob/eb4b84ad37d7e1e94165dcb966f7ed1d8114f508/dsl/camel-yaml-dsl/camel-yaml-dsl/src/test/groovy/org/apache/camel/dsl/yaml/KameletLoaderTest.groovy#L72]
> etc
> 3. Kamelet
> [properties|https://github.com/apache/camel/blob/eb4b84ad37d7e1e94165dcb966f7ed1d8114f508/dsl/camel-yaml-dsl/camel-yaml-dsl/src/test/groovy/org/apache/camel/dsl/yaml/KameletLoaderTest.groovy#L47]
> are in Camel Case.
> 4. Kubernetes part of Integration is also in Camel Case: *apiVersion*:
> camel.apache.org/v1
> I would like to propose to synchronize YAML DSL for the only one case: ex.
> Camel Case to be more Kubernetes standard oriented
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
