You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
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.
The text was updated successfully, but these errors were encountered: