As per the OAS 3.0.3 spec, for operation objects, operationIds must be unique:
Unique string used to identify the operation. The id MUST be unique among all operations described in the API. The operationId value is case-sensitive. Tools and libraries MAY use the operationId to uniquely identify an operation, therefore, it is RECOMMENDED to follow common programming naming conventions.
Considering the following spec - notice how the two operations share the same operationId: notUniqueOperationId. swagger-cli validate openapi.json returns openapi.json is valid.
However https://editor.swagger.io/ will properly report Semantic error at paths./pet.post.operationId Operations must have unique operationIds.
As per the OAS 3.0.3 spec, for operation objects, operationIds must be unique:
Considering the following spec - notice how the two operations share the same operationId:
notUniqueOperationId
.swagger-cli validate openapi.json
returnsopenapi.json is valid
.However https://editor.swagger.io/ will properly report
Semantic error at paths./pet.post.operationId Operations must have unique operationIds.