Open pyexplorerhs3 opened 1 month ago
There was a discussion about how to structure URLs for nested resources (e.g. tasks).
In my opinion we should stick to the convention with having both IDs (student ID and task ID) explicitly in the URL (/api/students/<student_id>/tasks/<task_id>
). An example would be /api/students/1/tasks/2
1
identifies the student and 2
identifies the taskapi/students/1/tasks
and enforce client to pass task_id
in the body payload
??Subject Discussion?? Pure REST endpoints without request.post or combine with both (Proposition from https://github.com/zetonteam/zeton_django/pull/110)