There are many ways to do this, from using a maven plugin in your build process to writing scripts to do the codegen merge. Not to make a product plug, but if you watch this:
https://youtu.be/SvDml_BChnE You’ll see another way using commercial tooling. > On Oct 5, 2016, at 3:45 PM, Gregg Fiehler <[email protected]> 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.
