Working with the Swagger toolchain, it’s clear that the Open edX APIs are not structured the way Swagger expects. For example, it categories both “/api/badges/v1/assertions” and “/api/bookmarks/v1/bookmarks” into “api”, and “/zendesk_proxy/v0” into “zendesk”.
When generating code with swagger-codegen, I get an “api_api.py” with dozens of endpoints, and a “zendesk_api.py” with two.
Maybe one way to solve this would be to have more than one swagger.yaml file? One for badges v1, one for bookmarks v1, and so on. I need some feedback from people who have used Swagger before. I feel like we are going against the grain in some way, but I’m not sure what is the right way.