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
Current implementation has more than 3 types of error responses in pinpoint web, and there is no written standards on how to handle error on failed requests.
I'd like to suggest throwing ResponseStatusException(throw new ResponseStatusException(HttpStatus.xxx, "error message")) when error occurs so that Spring can make the response data in its ErrorController.
This way, there is lower chance to see white label page error since front end will handle the responses with above format even when unexpected exceptions has occurred.
The text was updated successfully, but these errors were encountered:
ga-ram
added a commit
to ga-ram/pinpoint
that referenced
this issue
Jun 28, 2022
Current implementation has more than 3 types of error responses in pinpoint web, and there is no written standards on how to handle error on failed requests.
I'd like to suggest throwing ResponseStatusException(
throw new ResponseStatusException(HttpStatus.xxx, "error message")
) when error occurs so that Spring can make the response data in its ErrorController.error response example:
This way, there is lower chance to see white label page error since front end will handle the responses with above format even when unexpected exceptions has occurred.
The text was updated successfully, but these errors were encountered: