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 there!
I've noticed a behavior in the HTML report, When an operation parameter includes a schema reference and the schema itself is modified, both the path, operation and parameters are rendered in the diff editor tree.
For example, consider the following operation parameter:
If the schema is altered, the tree is displayed as follows:
The paths, operations, and parameters are rendered, although they are not clickable or altered. While this behavior might not be problematic with small OpenAPI specs, it becomes cumbersome and confusing when a schema is referenced across multiple operation parameters.
Hello there! I've noticed a behavior in the HTML report, When an operation parameter includes a schema reference and the schema itself is modified, both the path, operation and parameters are rendered in the diff editor tree.
For example, consider the following operation parameter:
If the schema is altered, the tree is displayed as follows:
The paths, operations, and parameters are rendered, although they are not clickable or altered. While this behavior might not be problematic with small OpenAPI specs, it becomes cumbersome and confusing when a schema is referenced across multiple operation parameters.
Is this behavior expected? Thanks! :)