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
At the moment, there is no change detection for operation IDs. Changing an Operation ID can break API clients, because the operation ID is usually the way to refer to a specific operation.
Example test case:
Before
openapi: "3.0.0"
info:
version: 1.0.0
title: Swagger Petstore
license:
name: MIT
servers:
- url: http://petstore.swagger.io/v1
paths:
/pets:
get:
summary: List all pets
operationId: listPets
responses:
'200':
description: A paged array of pets
default:
description: unexpected error
After
openapi: "3.0.0"
info:
version: 1.0.0
title: Swagger Petstore
license:
name: MIT
servers:
- url: http://petstore.swagger.io/v1
paths:
/pets:
get:
summary: List all pets
operationId: changed
responses:
'200':
description: A paged array of pets
default:
description: unexpected error
The output contains no changed operations, while the ID changed.
I am willing to create a pull request to add this feature.
The text was updated successfully, but these errors were encountered:
At the moment, there is no change detection for operation IDs. Changing an Operation ID can break API clients, because the operation ID is usually the way to refer to a specific operation.
Example test case:
Before
After
The output contains no changed operations, while the ID changed.
I am willing to create a pull request to add this feature.
The text was updated successfully, but these errors were encountered: