feat: Scheduling API Clients

[linnall]

Notion ticket link

Scheduling API Client

Implementation description

• Creating API clients for scheduling endpoints

Steps to test

1. Create dummy user

• POST to auth/register
  sample body: { "firstName": "Test", "lastName": "User", "role": "Donor", "email": "test@email.com", "phoneNumber":"8888888888", "password": "123456", "businessName": "Test Business" }
• login at http://localhost:3000/login

2. Create dummy button with onClick function that triggers the following api clients:

• SchedulingAPIClient.createSchedule
• SchedulingAPIClient.getSchedules
• SchedulingAPIClient.getScheduleById
• SchedulingAPIClient.updateSchedule
• SchedulingAPIClient.deleteSchedule

What should reviewers focus on?

Make sure requests are successful!

Checklist

• My PR name is descriptive and in imperative tense
• My commit messages are descriptive and in imperative tense. My commits are atomic and trivial commits are squashed or fixup'd into non-trivial commits
• I have run the appropriate linter(s)
• I have requested a review from the PL, as well as other devs who have background knowledge on this PR or who will be building on top of this PR

[linnall]

Note: Appears that I still need to accommodate for foreign key reference

[Shehryar21]

This is fine! In fact this is how it should be. To create a donation, you need to to be logged in and that donor should be in the donors table.

[linnall]

On a semi-related note, do we still allow the donorId property to be updated when we update a schedule? Or do we keep it so that the donorId stays consistent with whichever donor is logged in so they can only edit their scheduled drop-offs?

[Shehryar21]

donorId should not be updated and the Frontend will never pass donorId to the updateSchedule function / endpoint.