6-api-documentation #15
Merged
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
AsukaCHikaru
reviewed
Aug 6, 2019
Ananpipi
reviewed
Aug 6, 2019
dwi2
reviewed
Aug 6, 2019
|
|
||
| # TODO: | ||
| # We should create a package and move this into that package | ||
| @app.route('/photo', methods=['GET']) |
There was a problem hiding this comment.
This means after this patch, /photo is no longer working.
Can we also add an apis/photo.py to maintain compatibility?
There was a problem hiding this comment.
added by this commit 971363c
z6wdc
added
WIP
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have followed these two documents to reorg our api and generate automatically documentation.
And we can see our documentation by our end point URL.
https://flask-restplus.readthedocs.io/en/stable/scaling.html
https://flask-restplus.readthedocs.io/en/stable/swagger.html
This PR also included a
/memberapi that will return the member's json file.But I have not connected with our SQL.
I will create another PR for connecting our SQL and write a model for dealing with json file.