Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate OAS/Swagger generation of client #267

Open
LordMike opened this issue Apr 13, 2018 · 1 comment
Open

Investigate OAS/Swagger generation of client #267

LordMike opened this issue Apr 13, 2018 · 1 comment

Comments

@LordMike
Copy link
Collaborator

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

@LordMike
Copy link
Collaborator Author

LordMike commented Apr 5, 2021

The current OAS specs seem incomplete. For Movie f.ex., there are non of the "append_to_response" methods available as properties, so if we generated it from that, we would be missing those.

I suppose we could post-add those specifically, using partials.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant