Proper REST API Nesting
I feel like I am doing too much nesting. Do these routes look semantically correct overall? thanks!
GET
GET
POST
POST
DELETE
GET
PATCH
DELETE
PATCH
POST
POST
GET
GET
/courses (get course details of courses you are enrolled in)GET
/courses/:course_id (get specific course details, should this get everything related to the course?)POST
/courses (create new course)POST
/courses/enroll (attempt to join class only using course code)DELETE
/courses/:course_id (delete entire course)GET
/courses/:course_id/members (owner gets all members of their course)PATCH
/courses/:course_id/members/:user_id (change role of user in course)DELETE
/courses/:course_id/members/:user_id (leave a course)PATCH
/courses/:course_id/meetings/:meeting_id (updated details of a meeting)POST
/courses/:course_id/meetings (create a new meeting)POST
/courses/:course_id/meetings/:meeting_id (join the queue for this meeting)GET
/courses/:course_id/meetings/:meeting_id (get specific meeting details)