Skip to content
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

Merged
merged 20 commits into from
Jan 21, 2024
Merged

SAC-14 Update Tag Patch #35

merged 20 commits into from
Jan 21, 2024

Conversation

garrettladley
Copy link
Member

No description provided.

@garrettladley garrettladley requested review from a team, akshayd2020, michael-brennan2005 and DOOduneye and removed request for a team January 20, 2024 21:55
return err
}

return c.SendStatus(fiber.StatusNoContent)
Copy link
Contributor

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?

Copy link
Member Author

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)

Copy link
Member Author

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

backend/src/controllers/tag.go Outdated Show resolved Hide resolved
backend/src/controllers/tag.go Show resolved Hide resolved
backend/src/controllers/tag.go Outdated Show resolved Hide resolved
backend/src/services/tag.go Outdated Show resolved Hide resolved
backend/src/services/tag.go Outdated Show resolved Hide resolved
backend/src/services/tag.go Outdated Show resolved Hide resolved
backend/src/utilities/validator.go Show resolved Hide resolved
@garrettladley garrettladley merged commit 62e6293 into main Jan 21, 2024
6 checks passed
@garrettladley garrettladley deleted the SAC-14-Update-Tag-PATCH branch January 21, 2024 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants