F24/julia/activity management endpoints I

[liya-zhu]

Notion ticket link

Activity Management Endpoints I

Implementation description

• Added activity management endpoints
• Deleted redundant activity_id column from activity model
• Enabled auto-generated timestamps for created_at and updated_at columns in activity model
• Added activityUpdateDtoValidator with all fields optional so that any subset of fields can be updated
• Added date validator in backend/typescript/middlewares/validators/util.ts

Steps to test

1. GET /activities - Retrieves all activities.
   a. Accessible by Volunteer/Staff/Admin/Behaviourist
   

2. GET /activities/<id>- Retrieves a specific activity by its ID.
   a. Accessible by Volunteer/Staff/Admin/Behaviourist
   

   b. Invalid id
   

   c. id not in database
   

3. POST /activities - Creates a new activity. It can be created without a user and scheduled times.
   a. Not accessible by Volunteer/Staff roles
   

   b. Accessible by Admins and Behaviourists
   

   c. Creating without user, scheduledSartTime, startTme, endTime, notes
   

   d. Creating with required field missing (idk if this error message is misleading)
   

   e. Creating with invalid date
   

   f. Creating with invalid other fields
   

   g. Creating with non-existent petId, activityTypeId, or userId
   
   
   

4. PATCH /activities/<id> - Updates other details of an activity (generic endpoint).
   a. Not accessible by Volunteer/Staff roles
   

   b. Accessible by Admins and Behaviourists. Able to update any subset of fields
   

   c. Trying to set a required field to null
   

   d. Invalid id
   

   e. id not in database
   

5. DELETE /activities/<id> - Deletes an activity.
   a. Not accessible by Volunteer/Staff roles
   

   b. Accessible by Admins and Behaviourists
   

   c. Invalid id, id not in database tests are similar

What should reviewers focus on?

• The ticket asks for a patch endpoint but existing endpoints use put for updating entities. Not completely sure what the difference is but I used patch
• Should I merge/rebase on main

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

[trinity-y]

looks good to me other than that typo!!

[shencynthia]

Left a couple comments for small improvements but otherwise great work on this!! 🔥🔥🔥