-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enrollment (and content) endpoints should not 404 when no enrollments (or content) can be found #180
Comments
related, but maybe they worth another ticket:
we never return a 404 here, we always return a validation error as the
|
@thomasplevy
|
You are correct on the way all of these should be working |
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: