openapi

I'm very impressed by those docs. Anyone has insights how they were made? Looks like they were partly generated, otherwise it would be impossible to keep everything consistent - especially with the many language examples. They also seem to generate an OpenApi Spec (or use this as a basis for generating the docs?): https://github.com/stripe/openapi

> For example let's say you want to have access to Stripe subscriptions from Python I will use the official stripe flask checkout example[0]. > and cache them to your database, you'll need something like dj-stripe. There's nothing "in Python" other than an API client because the Python stdlib doesn't have a model ORM. With their OpenAPI definitions[1] to create the needed sqla model boilerplate, which creates the needed pgsql tables. For change log of my models it is kept in my py model files and xml with sql diff using a cheat where I implemented a Liquibase python wrapper[3]. I'm lucky where I work in a not to enterprise env so self-rolled solutions is sometimes acceptable and we try to keep it sane. [0]: https://stripe.com/docs/checkout/flask [1]: https://github.com/stripe/openapi [3]: https://github.com/Morabaraba/python-liquibase