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.
Creates the endpoint for time certification, and stores valid user-provided inputs into database
Logic flow: in the /reservation route, the "From" and "To" time buttons will trigger a dropdown modal so that the user can provide times for any selected date. This data will be sent and then the backend will perform certification tests:
After these tests are ran, they will update the Users, Rooms, and Buildings Database
NOTE: you may notice that I did not append new reservations to the end of reservations lists (good for you for noticing 🥳). it was designed this way so that if there is some sort of bug that may arise, we did not mutate the original list of reservations (i.e. this is an insurance policy)
ANOTHER NOTE: ReservationType now has a r_id field, date and times are no longer string types, rather they are Date and Time types. it made it a lot easier for me 😄