You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, setup_swagger is a one size fits all solution. It generates the swagger_def JSON file, then hosts a copy of swagger-ui (a.k.a. swagger_home).
I propose adding an option to decouple the two, so that it is possible to host just the swagger.json file, then the developer can choose to either self-host swagger-home or not to host it at all (if that is what they prefer). I am happy to make a PR to support this.
The text was updated successfully, but these errors were encountered:
Currently,
setup_swagger
is a one size fits all solution. It generates theswagger_def
JSON file, then hosts a copy of swagger-ui (a.k.a.swagger_home
).I propose adding an option to decouple the two, so that it is possible to host just the
swagger.json
file, then the developer can choose to either self-hostswagger-home
or not to host it at all (if that is what they prefer). I am happy to make a PR to support this.The text was updated successfully, but these errors were encountered: