[
https://issues.apache.org/jira/browse/CAMEL-15478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192178#comment-17192178
]
Claus Ibsen edited comment on CAMEL-15478 at 9/14/20, 10:25 AM:
----------------------------------------------------------------
apiProperties needs to be in more layers
apiName
description
+ methodName
+ signature
+ description
++ properties
So we have properties on the method level and high level description for api
and method as well.
Implement this for the source code generator of the configurer classes *DONE*
Implement this for the component json generator
was (Author: davsclaus):
apiProperties needs to be in more layers
apiName
description
+ methodName
+ signature
+ description
++ properties
So we have properties on the method level and high level description for api
and method as well.
> 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)
