Does anyone have recommendations for a day-to-day workflow for building and maintaining a multi-file swagger document that supports multiple versions of an API?
It's possible to create a new swagger file for each version (e.g. by changing the base path), but that may make it difficult to re-use resources, and it could be silly to have a whole new version when only a handful of responses changed. One solution would be to apply version prefixes for each resources or route (e.g. /api/users/v1.0.1/ or /api/users/v2.0.0/ or even /api/users/$latest/ ). As for workflow, is anyone aware of a schema editor that would help prevent human mistakes such as changing the response format for a resource? I.e. is there anything out there that would help alert us that we need to bump a major or minor version by evaluating the differences between response formats? -- Please NOTE: This electronic message, including any attachments, may include privileged, confidential and/or inside information owned by Leaf Group. Any distribution or use of this communication by anyone other than the intended recipient(s) is strictly prohibited and may be unlawful. If you are not the intended recipient, please notify the sender by replying to this message and then delete it from your system. Thank you. -- 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.
