Basic API backend for FrontEndTrivia (Sorry for delay!) #145
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 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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
As requested in PR FrontEndTrivia API / Backend #139, this is the same PR but directed at a different branch.
What is the current behavior? (You can also link to an open issue here)
Still needs some dev work. For example, what type of user information should be saved. Also, need to consider which routes will be needed by the frontend.
What is the new behavior (if this is a feature change)?
A basic API for FrontEndTrivia can be run.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Doesn't break anything since no endpoints are pointed to the API at the moment.
Other information:
Tech stack: