change management for api implementation with swaggerhub codegen
I love the codegen features in SwaggerHub. I want to build my api implementation on top of the generated boilerplate (python/flask in my case). But how do I handle changes? When I change the api and codegen the server stub do I need to cut and paste my existing implementation in to the new stub, and then adjust my implemenation? It seems like there must be some way to deal with this intelligently so I don't have to cut and paste my implementation into the new server stub every time I rev the api. Thanks for any advice! MarkBetter Model Documentation / Generation
It would be very useful Models could be given tags so that the documentation could group them the same way that the endpoints are grouped. Then in model generation, instead of all of the models in the model folder, they could be split up into sub folders in the model folder. Not sure if this is swaggerhub Idea, or more for the swagger-generation/swagger-editor repositories, but this is something I would like swaggerhub to do.