[
https://issues.apache.org/jira/browse/CAMEL-15478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17188428#comment-17188428
]
Claus Ibsen edited comment on CAMEL-15478 at 9/1/20, 1:27 PM:
--------------------------------------------------------------
api component generator of enums generate them with UPPERCASE("human name
here") kind.
So it would be good for the json metadata tooling to handle this, so it can use
the "human names" as its enums in the generated schema instead of the ugly
uppercased.
As workaround we have sometimes manually added enums="aaa,bbb,ccc" in the
source code. But lets make the tooling smarter. See the api components such as
twillio
*DONE*
was (Author: davsclaus):
api component generator of enums generate them with UPPERCASE("human name
here") kind.
So it would be good for the json metadata tooling to handle this, so it can use
the "human names" as its enums in the generated schema instead of the ugly
uppercased.
As workaround we have sometimes manually added enums="aaa,bbb,ccc" in the
source code. But lets make the tooling smarter. See the api components such as
twillio
> camel-api-component - Add label qualifier for api methods in generated
> configuration classes
> --------------------------------------------------------------------------------------------
>
> Key: CAMEL-15478
> URL: https://issues.apache.org/jira/browse/CAMEL-15478
> Project: Camel
> Issue Type: New Feature
> Components: tooling
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.6.0
>
>
> For example twillio has 30+ api methods where each has its own set of
> configuration class with UriParam options.
> We should add label=xxx for those generated UriParam that tell what api they
> are from. This allows end users to better see this in the documentation,
> which we can then include all of these now as well, so there will be a lot
> more options to see in the docs.
> We could also add a new attribute to UriParam like apiMethod or qualifier or
> something to seperate this and make the doc generator build a table for each
> api separately. This may make it nicer.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
