Skip to content

JSON API 1.1: status codes for specific responses #552

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.

Sign up for GitHub

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

Jump to bottom
Closed
n2ygk opened this issue Jan 7, 2019 · 2 comments
Closed

JSON API 1.1: status codes for specific responses #552

n2ygk opened this issue Jan 7, 2019 · 2 comments

Comments

@n2ygk
Copy link
Contributor

n2ygk commented Jan 7, 2019

See #547. Analyze newly-documented status codes for specific responses: json-api/json-api#1036 & json-api/json-api#1029
@sliverc
Copy link
Member

sliverc commented Jan 14, 2019

  • Delete of nonexistent resource should already lead to a 404 as this is the default behavior of DRF. Test needs to be added though
  • Referencing an nonexistent related resource currently leads to an 400 error. This will need to be changed (might be a bit tricky...)

@sliverc
Copy link
Member

sliverc commented Oct 4, 2019

Closing as explained at #547 (comment)

Once JSON API spec is moving forward we need to double check which issue need to be reopened.

@sliverc sliverc closed this as completed Oct 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sliverc @n2ygk