You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mmm well no to me it meant that the enrollments did not exist, so it's my wrong understanding of the specs: BUG.
Maybe the spec could be more "complete" if they said what was the actual resource that couldn't be found.
The following endpoints must be updated to respond with a 200 (not a 404) when no enrollments (or content) are found:
GET /memberships/{id}/enrollments
GET /courses/{id}/enrollments
GET /courses/{id}/content
GET /sections/{id}/content
The spec (for all endpoints) should be updated to note that the "resource" that is not found by the 404 is the course, membership, etc... and not the list enrollments
The text was updated successfully, but these errors were encountered:
thomasplevy
changed the title
Mmm well no to me it meant that the enrollments did not exist, so it's my wrong understanding of the specs: BUG.
Enrollment (and content) endpoints should not 404 when no enrollments (or content) can be found
Jul 2, 2020
Mmm well no to me it meant that the enrollments did not exist, so it's my wrong understanding of the specs: BUG.
Maybe the spec could be more "complete" if they said what was the actual resource that couldn't be found.
I did the same with:
they must be fixed then! Sorry!
Originally posted by @eri-trabiccolo in #178 (comment)
See related #178
The following endpoints must be updated to respond with a 200 (not a 404) when no enrollments (or content) are found:
GET /memberships/{id}/enrollments
GET /courses/{id}/enrollments
GET /courses/{id}/content
GET /sections/{id}/content
The spec (for all endpoints) should be updated to note that the "resource" that is not found by the 404 is the course, membership, etc... and not the list enrollments
The text was updated successfully, but these errors were encountered: