Jc/event controllers v2

[jcharlpretorius]

Event controllers:

• Created basic CRUD controllers (without file upload)
• Can create verified and regular (non verified) events. Verified events are associated with an organization
• Checking user permissions and event ownership currently being done inside controllers
• Added a controller with cursor based pagination for recent events. In the future we can use things like timestamp or id as the cursor, depending on how we want to order the results. I used cursor-based pagination instead of offset pagination because offset pagination does not scale well with db size. Pagination parameters are sent via query params: ?pageSize=<>&cursor=<>
  example using timestamp as cursor:
  First query, no cursor: api/events/recent/?pageSize=2

{
  "data": [
  {most recent event data...},
  {2nd most recent event data ...}
  ],
  "cursor": "2024-01-22T21:32:20.539Z"
}

Subsequent pages: api/events/recent/?pageSize=2&cursor=2024-01-22T21:32:20.539Z

{
  "data": [
  {3rd most recent event data...},
  {4th most recent event data...}
  ],
  "cursor": "2024-01-22T21:22:01.911Z"
}

When we reach the end of the available events the cursor is null

{
  "data": [],
  "cursor": null
}

Organization Controller with Default Role Permissions

• Added a 'create organization' controller with Prisma transaction for adding the user as the 'Owner' and adding all of the default roles and permissions into the database. This is a bit rough right now but adequate for testing user permission functionality

[AarshShah9]

You killing it with these PRs! I suggested a couple things that we can discuss in the meeting today. As long as we align with Noman I think this is all great