You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an invalid JSON is provided in the updatedBetween query parameter, the endpoints return a 500 Internal Server Error instead of a more appropriate 400 Bad Request.
Proposed Improvement
Add specific error handling for JSON parsing of updatedBetween parameter to return 400 Bad Request with a descriptive message when the input is malformed.
Implementation Details
Add try-catch block around JSON.parse
Return 400 Bad Request with descriptive message on parsing failure
Apply the improvement consistently across all endpoints that accept updatedBetween parameter
Current Behavior
When an invalid JSON is provided in the
updatedBetween
query parameter, the endpoints return a 500 Internal Server Error instead of a more appropriate 400 Bad Request.Proposed Improvement
Add specific error handling for JSON parsing of
updatedBetween
parameter to return 400 Bad Request with a descriptive message when the input is malformed.Implementation Details
updatedBetween
parameterReferences
/cc @MantisClone
The text was updated successfully, but these errors were encountered: