You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The only change is for the inner object Schema1, where its property changed from integer to string. This should be considered a breaking change, however oasdiff ignores the change completely.
When changing the return schema from Schema2 to Schema1, the change is detected and reported as breaking as it should.
To Reproduce
Steps to reproduce the behavior:
Copy the 2 OpenAPI schemas above to files spec1.json and spec2.json
oasdiff breaking spec1.json spec2.json
Output is empty
Expected behavior
Correct output should be the same when changing the response schema to schema1:
error [response-property-type-changed] at spec2.json
in API GET /value
the 'property1' response's property type/format changed from 'string'/'' to 'integer'/'' for status '200'
Desktop (please complete the following information):
OS: macos 14.6.1
oasdiff version 1.10.23
The text was updated successfully, but these errors were encountered:
This is due to additionalProperties which is used in Schema2.
Oasdiff doesn't currently support breaking changes for additionalProperties.
I am going to change this issue type from a bug to an enhancement to remind myself or another kind contributor to add support for additionalProperties.
Describe the bug
Comparing the following 2 OpenAPI schemas:
And:
The only change is for the inner object
Schema1
, where its property changed from integer to string. This should be considered a breaking change, howeveroasdiff
ignores the change completely.When changing the return schema from
Schema2
toSchema1
, the change is detected and reported as breaking as it should.To Reproduce
Steps to reproduce the behavior:
oasdiff breaking spec1.json spec2.json
Expected behavior
Correct output should be the same when changing the response schema to
schema1
:Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: