Skip to content

Investigate OAS/Swagger generation of client #267

Description

@LordMike

On the V4's documentation page, there are links to OAS / RAML specs for the API. We could generate a lot of code from these specifications, and then code the few differentiations there are for an actual client (overloads and whatnot) -- I imagine we'll also encounter cases where two responses/requests use the same object, but where the spec specifies different objects.

However, currently (was also the case last I tried swagger on this) the spec is incomplete or invalid: https://www.themoviedb.org/talk/58691a749251414e7500c442

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