openapi-changes icon indicating copy to clipboard operation
openapi-changes copied to clipboard

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

Results 82 openapi-changes issues
Sort by recently updated
recently updated
newest added
trafficstars

it s fair to detect change in the example section like addition , change , or removal it is unfair to set that a examples removal is a breaking change...

when doing change and it does not introduce breaking change , it should still display breaking but set the value to 0 ![image](https://github.com/pb33f/openapi-changes/assets/12461661/31f07380-de40-40c2-ba97-938f53eaa3a2) should be as same as this ![image](https://github.com/pb33f/openapi-changes/assets/12461661/d3d20144-1fbf-4ea6-b5ec-06af3d1d292f)...

not sure about the UX for that can be a filter show all , breaking change only can be with tiny arrows to navigate to the next breaking change the...

given 2 files one having an AllOf of properties A and B anf one having 2 fields , openAPI change should detect that there is a change but non breaking...

adopt a convention for original vs modified in a consistent maner i would say updte that on the left it is the original and on the right the modified so...

given i am launching openAPI changes one several files i would like to be able to specify the name of the report openapi-change A.yaml B.yaml toto.html or can be leveraging...

given openapi-changes.cmd html-report D:\tot\a.yml D:\toat\b.yml i got the following ` DONE completed processing WARNING warnings reported during processing ⚠️ unable to parse modified document: unable to parse specification: yaml: line...

![image](https://github.com/pb33f/openapi-changes/assets/12461661/c20a01ae-5b54-4bff-a8d3-16afe512ffcf) here looks like the fact there is a URL in the description put the situation up side down cf text description

I'm trying to include openapi-changes in our GitHub Actions CI to detect breaking changes in pull requests. My approach to doing this was to take the number of commits made...

I am seeing issues with a schema that uses JSON pointer in the current dependency configuration of `openapi-changes`: ``` ERROR component '#/components/schemas/OneOrMany' does not exist in the specification Error: unable...