This repository has been archived by the owner on Jun 10, 2024. It is now read-only.
[EXPERIMENTAL] swagger using flasgger #23
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
closing since restx was preferred |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is one of two competing PRs that achieve the same thing. You should read them and compare! The other one is #21.
This uses flasgger to integrate Swagger. I haven't fleshed out the documentation yet; this is a minimal integration that gets everything working.
As you can see, this is more explicit, and requires less reworking of application code -- at the expense of having to hand-roll docstrings everywhere. My definition of request and response bodies is lazy here, and could use a little more thought, but you get the gist.