openapi-changes
openapi-changes copied to clipboard
pb33f
The world's sexiest OpenAPI breaking changes detector. Discover what changed between two OpenAPI specs, or a single spec over time. Supports OpenAPI 3.1, 3.0 and Swagger
Hello again, still a big fan of these tools! I've discovered that if the spec you start from lacks a components property and then you compare with a spec that...
First of all the tool works , an helps definitely when doing a massive refactoring  here the enhancement is when there is a diff here between something expended on...
@daveshanley there are 2 levels that could be applied 1) identify each rules via an identifier and have the capability to have flag : off; info, warning, breaking 2) capability...
When a breaking change is made is a api spec json, it will never return an exit code to make a pipeline fail. Thus the pipeline will always succeed even...
here i have on top o bject added: /v1/api/trade-blotter/trade-views to path and below image h but in same situation i have on top object added: /v1/api/trade-blotter/trade-views/{viewId} to path  issue...
here the only difference is the field ordering (eq , neq )  properties: field: type: string description: | Label of the parameter to filter on. in: $ref: '#/components/schemas/operatorArray' nin:...
be able to spot that it is semantically compatible operator: anyOf: - type: string - type: number - type: 'null' vs operator: type: - null - string - number notice...
given an endpoint with a query parameter parameters: - $ref: '#/components/parameters/query_calibrationResultId' given query_calibrationResultId: name: calibrationResultId description: | Calibration result in which the resource(s) will be queried. in: query schema: type:...
required ; - a - b and required : - b - a should not be considered as a difference even not a warning or noticed
OpenAPI Changes does not have the option to write out the report to a specific file, rather than to console. It would be great for CI/CD to be able to...
