#106 Store Users in the DB #120
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
Closed
thomastai1666
approved these changes
Nov 16, 2021
Jen-Lopez
force-pushed
the
store-users
branch
from
26049e3 to
1f42816
Compare
Co-authored-by: Thomas Tai <[email protected]>
Co-authored-by: Thomas Tai <[email protected]>
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.
This PR stores the user in the database and maps it to a current existing group based on the invite code (aka id).
NOTE: We're temporarily using a hardcoded group ID to map the user with a group. This will be replaced by #73, which is blocked by lack of other routes.
ANOTHER NOTE: This should be merged in after all the other PRs. In reality, only 2-3 files are changed:
back-end/app.js,front-end/src/pages/User.jsx