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
I discussed this a bit in a blog
post:
https://blog.codeship.com/json-schemas-role-in-building-and-deploying-your-api/
I put together a sample repo for
it: https://github.com/fireproofsocks/swagger-multifile-examples
On Thursday, August 31, 2017 at 5:30:48 AM UTC-7, ch...@unomicedge.com
wrote:
I just started using Swagger and noticed something different between the
local editor/old editor and the online editor.
Is that something that should really happen? Shouldn't this be related to
swagger version instead of the editor that i'm using?
I'm not using tags and in the local editor/ol
Using Math.Random() is not a secure way of generating random numbers. They
cannot withstand cryptographic attacks by hackers.
This is being reported by fortify from swagger-UI.js
Is there a fix for this or a patch or explanation for the issue.
SwaggerUi.Views.ParameterContentTypeView = Backbone
