Many of them have already been implemented, make sure to add functionality to only perform the action on a calendar that is passed on as a URL parameter, e. g. DELETE /api/aets/:id/:calendarid. This doesn't replace the AET id that is passed on in the request body, you should just check if the AET belongs to the calendar.
[ ] Add the necessary frontend fetches to the API, i. e., add a way to add, remove, and edit AETs from the frontend via doing an HTTP request to the server and only applying the deletion, creation, or edit if the server was able to delete, create, or edit the AET in the database.
[x] Finish Rest API routes for AETs
Add AET
Remove AET
Update AET
Many of them have already been implemented, make sure to add functionality to only perform the action on a calendar that is passed on as a URL parameter, e. g.
DELETE /api/aets/:id/:calendarid. This doesn't replace the AET id that is passed on in the request body, you should just check if the AET belongs to the calendar.