This repository has been archived by the owner on May 25, 2020. It is now read-only.
Moving over to using Flask blueprints #15
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
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.
So I changed the structure over to using blueprints. The reason for this is they allow scalability and give us a lot of flexibility. We are now able to have separate versions of the API if we decided to change endpoints or add on more APIs.
Other changes include making the app is just a function inside of the
__init__.py. Inviews.pyyou can create another endpoint and it will automatically get added to the API's blueprint. All endpoints (or a.k.a. Resources) now need to contain a static variable of their endpoint path.Also removed one textbook endpoint when no term is entered. Since it requires figuring out what the current term is.