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
This is maybe more a question - using allOf structures with json schema you will have to repeat the properties from the previous sibling schemas as empty properties in the last of the allOf schemas in order to ensure that the properties are allowed and that you are able to set additionalProperties to false on the last schema to avoid allowing consumers to send irrelevant data.
I don't see that approach anywhere in you OAS so I am wondering how you have solved the problem of not allowing additional properties to be send and at the same Tim be able to validate that the json sent is compliant to the total schema of the allOf.
The text was updated successfully, but these errors were encountered:
This is maybe more a question - using allOf structures with json schema you will have to repeat the properties from the previous sibling schemas as empty properties in the last of the allOf schemas in order to ensure that the properties are allowed and that you are able to set additionalProperties to false on the last schema to avoid allowing consumers to send irrelevant data.
I don't see that approach anywhere in you OAS so I am wondering how you have solved the problem of not allowing additional properties to be send and at the same Tim be able to validate that the json sent is compliant to the total schema of the allOf.
The text was updated successfully, but these errors were encountered: