-
Notifications
You must be signed in to change notification settings - Fork 0
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
SAC-14 Update Tag Patch #35
Conversation
backend/src/controllers/tag.go
Outdated
return err | ||
} | ||
|
||
return c.SendStatus(fiber.StatusNoContent) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we be returning a no content status code? I guess it's fair but giving some key back for success to the frontend might be good @alderwhiteford mr error code god whats your opinion?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From what I've seen on the semantics sending a 204 (fiber.StatusNoContent
), it means "although the server successfully processes the request, there's no additional content or response payload body that needs to be returned to the client. In essence, a 204 status code conveys 'I've done what you asked, and there's no more information to give you.'" (Abstract API)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not to be the contrarian but what would we send back? What information would the frontend need on update or delete? From my perspective, just whether it happened, or not
No description provided.