Closed exejutable closed 4 years ago
This won't be implemented, because the OpenAPI specification says:
operationId is an optional unique string used to identify an operation. If provided, these IDs must be unique among all operations described in your API.
Alternatively, we can add support for x-operation-name
from Loopback. Would that be an option?
I see, okey we can go for the second one, add funtionality. I check the doc of openapi , we can extend the spec respecting the rules they propose.
Today if the operationId is repeated add a suffix to the name for example:
this create two services
users
with the methodfind
and the serviceorganizations
with the methodfind_1
. Maybe we can change this to make the combination oftag
andoperationId
unique to prevent the suffix in this cases?