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
I've discovered that if the spec you start from lacks a components property and then you compare with a spec that has components added, running the summary command will cause a crash. Adding an empty components property to the starting spec fixes the problem.
Interestingly enough HTML report generation seems to work correctly without the empty property.
Here's a zip file with some minimal reproduction specs: examples.zip
(Note: adding an empty components property to the new file will also cause the crash but I've added a mock schema to be more correct to the real use case that produced the error)
And here is the command and result of running against the attached files:
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 has components added, running the summary command will cause a crash. Adding an empty components property to the starting spec fixes the problem.
Interestingly enough HTML report generation seems to work correctly without the empty property.
Here's a zip file with some minimal reproduction specs: examples.zip (Note: adding an empty components property to the new file will also cause the crash but I've added a mock schema to be more correct to the real use case that produced the error)
And here is the command and result of running against the attached files: