Open Oracking opened 2 years ago
Currently, there is no support for nested fields when specifying the request/response schema.
E.g. If I specify a schema like: {"name": "string", "countries": ["string"]}, it causes an invalid swagger to get generated
{"name": "string", "countries": ["string"]}
An invalid swagger is generated for both cases: supplying the schema as a dict or as a Marshmallow schema.
I will start a feature branch for this
what about this ?
Currently, there is no support for nested fields when specifying the request/response schema.
E.g. If I specify a schema like:
{"name": "string", "countries": ["string"]}
, it causes an invalid swagger to get generatedAn invalid swagger is generated for both cases: supplying the schema as a dict or as a Marshmallow schema.