Regardless of the properties-property that might be present in the schema for an encoding in requestBody, all properties must be passed to the route handler function.
Relevant spec
The properties is not mandatory and additionalProperties, which handles not explicitly listed properties defaults to true.
At the moment Roaster will only pass properties to the route handler that are explicitly listed as if additionalProperties was set to false. This is true for form-data and needs to be checked for other encodings as well.
Example requestBody definition:
{
"requestBody": {
"content": {
"application/json": {
"schema": {
"type": "object"
}
},
"application/x-www-form-urlencoded":{
"schema": {
"type": "object"
}
},
"multipart/form-data":{
"schema": {
"type": "object"
}
}
}
}
Regardless of the
properties-property that might be present in the schema for an encoding in requestBody, all properties must be passed to the route handler function.Relevant spec
The
propertiesis not mandatory andadditionalProperties, which handles not explicitly listed properties defaults totrue.At the moment Roaster will only pass properties to the route handler that are explicitly listed as if
additionalPropertieswas set tofalse. This is true for form-data and needs to be checked for other encodings as well.Example requestBody definition:
{ "requestBody": { "content": { "application/json": { "schema": { "type": "object" } }, "application/x-www-form-urlencoded":{ "schema": { "type": "object" } }, "multipart/form-data":{ "schema": { "type": "object" } } } }