Your descriptions are pretty much right.
There’s no overlap between the tools as they use each other. The Editor uses the UI for rendering (so you can get live feedback of what you’re creating) and it uses the codegen to generate the code. From: <[email protected]> on behalf of mkim <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Monday, December 11, 2017 at 16:53 To: Swagger <[email protected]> Subject: Use Cases for Swagger Editor/UI/Codegen? Hi, I'm quite new to swagger and I’ve spent some time researching the tools. I'm still in the process of setting the tools up so I haven't been able to play with them fully(IT restrictions!). It’s not 100% clear to me the usage/benefits of Swagger UI standalone, as well as the differences between the tools. Can someone tell me if I’m on the correct line of thinking? Swagger Editor: Both the editor and UI for superficial testing of the API. Can stub both server and client side implementations (which uses Swagger Codegen?). Swagger UI: Hosted documentation of API spec that is being served. Can be used for testing the actual service. Swagger Codegen: Stub both server and client side implementations, as well as documentation generation. Seems like there’s quite a bit of overlap. Am I missing key strengths of each tool that would require them to be standalone, as opposed to just setting up Swagger Editor on my local machine? Thanks! -- 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. -- 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.
