PUT / Update Community-Event API

[anjolaoluwaakindipe]

Created the update API following the structure created by @1234tgk and also added validation to the to the update api to prevent invalid user requests

Example of Request:

Post request created by @1234tgk on the left and put request created by me on the right

Additions

1. Added Zod as a dependency in the backend
2. Added a new error handling middleware which helps handle all types of errors both Custom and Unexpected src/middleware/errorHandler.ts
3. Added various Custom Application Errors src/utils/errors that can be used to throw Custom Errors within the application with already configured status codes. e.g BadRequestError, InternalServerError, ConflictError, UnauthorizedError, and NotFoundError.
4. Created a flexible validation parser function that validates requests based on any schema it is given and returns back the request (with type-safety based on the schema) if validation is successful, else throws an application error (BadRequestError) (src/utils/validation/validationParser.ts)
5. Added JsDoc comments in a few files
6. Renamed some of the exports and imports to be more explicit. e.g

Before:

export default {
   create: (req, res) => {...}
}

After:

const communityEventController ={
    create: (req,res) => {...}
}
export default communityEventController

[0916dhkim]

Looks great! I love the validation system 👍
I left some suggestions below, so let me know what you think.

[igMike-V]

When we create a new event can we set the POST to have nobody? We should create a new empty event and then immediately load it into an event edit page to fill in the details.

So we would need only to return the id on the creation of an event.

What does everyone think?

[igMike-V]

just looked further at the code. Looks like what I just posted would work based on the validation schema

[anjolaoluwaakindipe]

When we create a new event can we set the POST to have nobody? We should create a new empty event and then immediately load it into an event edit page to fill in the details.

So we would need only to return the id on the creation of an event.

What does everyone think?

So should we make the requirement of a community event needing a user(organizer) optional for now?

[0916dhkim]

@igMike-V That is a good point 👍 I'll merge this PR and have the following issue for the fixes.

• Make some fields optional in CommunityEvent table #116