Summary: We merged the frontend add on call shift ticket with the add overnight shift ticket. Then, we built off of that and completed the backend #159 ticket, which was to add on-call shift to the database.
Testing: We tested this by adding regular and on-call shifts to the calendar and then confirming successful adds by checking rapid api.
Reflection: Overall, the tickets went well. We had one question about the use of urlParams in the on-call-shifts POST route. We commented out that code, but we're not sure if it is necessary or preferred.
Developers: Sean and Carly Time Spent: 1.5 hours
Summary: We merged the frontend add on call shift ticket with the add overnight shift ticket. Then, we built off of that and completed the backend #159 ticket, which was to add on-call shift to the database.
Testing: We tested this by adding regular and on-call shifts to the calendar and then confirming successful adds by checking rapid api.
Reflection: Overall, the tickets went well. We had one question about the use of urlParams in the on-call-shifts POST route. We commented out that code, but we're not sure if it is necessary or preferred.