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
One some schemas I want to provide additionalProperties and have explicitly set that.
I think it would be beneficial if the schema contract test which adds additionalProperties:false is aware of explicitly set objects as a way of working with this feature
The text was updated successfully, but these errors were encountered:
Could you give us some more context?
Or an example of what the outcome was, while you expected something else?
schemaValidation (Boolean) : Adds the test if the response body is matching the JSON schema defined in the OpenAPI spec. The JSON schema is inserted inline in the Postman test.
additionalProperties
(Boolean) : Extend the expected JSON schema used for the schemaValidation by setting all the additionalProperties.
One some schemas I want to provide additionalProperties and have explicitly set that.
I think it would be beneficial if the schema contract test which adds additionalProperties:false is aware of explicitly set objects as a way of working with this feature
The text was updated successfully, but these errors were encountered: