Skip to content

No support for nested fields in Schema specification #11

@Oracking

Description

@Oracking

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

An invalid swagger is generated for both cases: supplying the schema as a dict or as a Marshmallow schema.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions