#886 [GOOD FIRST ISSUE] Standardize Global Error Response Payload Structure#1149
Closed
Meek-Maestro wants to merge 0 commit into
Closed
#886 [GOOD FIRST ISSUE] Standardize Global Error Response Payload Structure#1149Meek-Maestro wants to merge 0 commit into
Meek-Maestro wants to merge 0 commit into
Conversation
Owner
|
@Meek-Maestro please resolve conflicts |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#886 [GOOD FIRST ISSUE] Standardize Global Error Response Payload Structure
Description
Replaced all manual
res.status().json()error responses throughout the codebase with centralizedthrow createError()calls using standardizedERROR_CODES. This ensures consistent error response formatting and enables the global error handler middleware to manage all error responses uniformly.Related Issue
Fixes #886
Type of Change
Changes Made
res.status().json()error responses withthrow createError(ERROR_CODES.XXX, ...)requireAdmin,requireSuperAdmin)Checklist
Screenshots (if applicable)
N/A
Additional Notes
Health check endpoints (e.g.,
/ready,/health) that intentionally return dynamic status codes (200/503) were kept as-is since they represent expected states rather than error conditions.