Members of the swagger team build https://swaggerhub.com which is tackling this problem directly.
> On Nov 22, 2016, at 11:51 AM, Jeff Lowery <[email protected]> wrote: > > There are some slides here > <http://www.slideshare.net/olensmar/swagger-intheapilifecycle>, but not very > specific... you have to read between the lines. I also saw an issue posted > somewhere about this topic and it was acknowledges by the Swagger team, so > maybe more thought will be put in it. > > On Wednesday, October 5, 2016 at 3:45:01 PM UTC-7, Gregg Fiehler wrote: > Hi, > I wanted to hear how some people handle the full lifecycle of an api when > using codegen for the server. > > Scenario: > create new api using swagger editor > use swagger.json and codegen to generate server stub (java spring-mvc, but it > could be others) for api > write business logic > deploy api > business request to update api with new features > ??? what is the best way to do this: > update yaml file with changes and generate new stub and copy existing > business logic to new code > write new code into existing code base and then generate new swagger.json > from code > ... > Trying to understand the options of how to handle this when using code > generation. > > Any suggestions and experiences would be appreciated. > > Gregg > > -- > You received this message because you are subscribed to the Google Groups > "Swagger" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
