#3 backend user schema + api routes #19
Merged
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.
Description
Made the User schema and User CRUD, also made a simple form to test!
Issues
#3
Screenshots
Test
-Create a User with the form, fetch the user with fetch button, update the user with the update button, and finally delete the user.
-For each step check MongoDB collection for both User and VolunteerDetails
Possible Downsides
-Whenever we return a User, we return the user and volunteerDetails in a separate object.
-When we create the User it does not have the Events field until we update.
Additional Documentations