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
given an API diff change got this errpr openapi-changes version: 0.0.62 | compiled: Thu, 25 Apr 2024 16:39:09 UTC DONE starting console... panic: runtime error: slice bounds out of range...
Doing openapi-changes **report** a.yml b.yml it returns raw json {"message": "No changes found between specifications"} when leveraging summay there is no output when leveraging console it looks a bit broken...
given 2 files , if i generate a report =A , and then fo a second report B A and B are different, the order is not the same ,...
I would like to also see the `path` from `summary` starting with `SPEC:` in the `report` feature.
Is the `reportSummary` wrong? I see only one `totalChanges` and zero `breakingChanges`. But in `changes` are two entries, one with `breaking` `true`. Only `openapi` and `version` are changed. The generated...
given the command line openapi-changes html-report 1.yaml 2.yaml when i display a a diff  i would expect to not have original and not available , but 1.yaml and 2.yaml...
running the command like this return poor feedback ``` openapi-changes --version Error: unknown flag: --version ``` here should be harmonized and go to same answer than > openapi-changes --help
given the snippet ``` schemas: Pet: type: object properties: id: readOnly: true type: string name: type: string enum: - Bob ``` and this snippet ``` schemas: Pet: type: object properties:...
Would it be possible to write error messages in a machine-readable json format? As example if I try to compare swagger v2 with v3 I would like a json like...
If the feature is missing and I'm not just too stupid to find out how to do it: Converting an already generated `report`.json to a report.html via `html-report` would be...