Revamp API return codes for empty responses #146

Closed
opened 2021-10-27 12:58:01 -04:00 by JoshuaBoniface · 1 comment
JoshuaBoniface commented 2021-10-27 12:58:01 -04:00 (Migrated from git.bonifacelabs.ca)

One good change would be leveraging 204 to indicate that a request had no content rather than just sending back an empty array. Let the client decide how to present this.

Also leverage 202 where appropriate (I may already be).

406 might also be useful for some of the curent 400 bad request endpoints.

One good change would be leveraging 204 to indicate that a request had no content rather than just sending back an empty array. Let the client decide how to present this. Also leverage 202 where appropriate (I may already be). 406 might also be useful for some of the curent 400 bad request endpoints.

Most of these end up being pointless changes. Not going to bother.

Most of these end up being pointless changes. Not going to bother.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: parallelvirtualcluster/pvc#146
No description provided.