You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Aljaž Plohl (Jira)" <ji...@apache.org> on 2020/09/08 11:46:00 UTC
[jira] [Commented] (CAMEL-15514) camel-rest-openapi component
automatic operationId generation
[ https://issues.apache.org/jira/browse/CAMEL-15514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192165#comment-17192165 ]
Aljaž Plohl commented on CAMEL-15514:
-------------------------------------
I have created this issue to be able to submit a Github PR, as I have already implemented this improvement.
> camel-rest-openapi component automatic operationId generation
> --------------------------------------------------------------
>
> Key: CAMEL-15514
> URL: https://issues.apache.org/jira/browse/CAMEL-15514
> Project: Camel
> Issue Type: Improvement
> Components: camel-rest-openapi
> Affects Versions: 3.x
> Reporter: Aljaž Plohl
> Priority: Minor
>
> Upon using camel-rest-openapi component in a route, I have discovered that if an operationId is not defined in OpenApi specification the operation can not be called.
> Since operationId is an optional parameter as defined by OpenApi 3 standard, I think that improving the component to be able to auto generate missing operationIds from operation path and http method would benefit users of this component.
> As an example, you can find one published OpenApi specification that does not define operationIds: [https://app.swaggerhub.com/apis/liferayinc/commerce-admin-catalog/v1.0#/info|https://app.swaggerhub.com/apis/liferayinc/commerce-admin-catalog/v1.0#/info]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)