operationId

[okutyrin]

Is it possible to generate operationId as a part of OpenAPI definition? While it is optional from the POV of OpenAPI spec, some clients (https://github.com/swagger-api/swagger-js) rely on its existence.
Thanks!

[ralfhandl]

@okutyrin It is possible, however https://github.com/swagger-api/swagger-js#tags-interface says that it can work without operationIds:

• If an operationId is missing, we deduce it from the http method and path, i.e. ${method}${path}, with non-alphanumeric characters escaped to _. See these tests (1, 2) for examples.

I could do something similar, using $ as a separator character because it is not allowed in OData names and is allowed in JavaScript identifier names:

anEntitySet$$c
antEntitySet$$r
anEntitySet$$key$$r
anEntitySet$$key$$u
anEntitySet$$key$$d
anEntitySet$navProp$$r
anEntitySet$collectionNavProp$$c
anEntitySet$collectionNavProp$$r
anEntitySet$collectionNavProp$$key$$r
anEntitySet$collectionNavProp$$key$$u
anEntitySet$collectionNavProp$$key$$d
anEntitySet$collectionNavProp$$key$secondLevelNavProp$$r

etc.

Can you check whether that would work for your downstream tools?

Thanks in advance
Ralf

[okutyrin]

can work without operationIds

Yes, in theory. But the way how they deduce operationIds out of existing tags results sometimes in ambiguous IDs, which is sort of bad ;)

Can you check whether that would work for your downstream tools?

Sure, will give it a try.

[ralfhandl]

Hi @okutyrin,

The examples in branch operationid now have operationIds, see https://github.com/oasis-tcs/odata-openapi/tree/operationid/examples.

Can you please check whether that works for your client tools?

If it does, I will merge this into master.

Thanks in advance
Ralf