-
Notifications
You must be signed in to change notification settings - Fork 881
Consistently display error messages from backend #1943
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
Comments
I think this should be an epic with one ticket per XService. I'd like to work on it because I already put some thought and code into it, but I don't think it's a high enough priority for pre-launch. |
Deliverable for this sprint would be to create the Epic and shred it into its issues |
Let's pick these off to complete as we get time. These are not high priority but should get attention as we go. |
Seems like this issue is decomposed, so I'm going to close it in favor of the others. They'll still reference this so the context isn't lost. |
As was done in the
usersXService
, we should go through the frontend and make sure all error messages from the API are being unpacked properly to avoid over-reliance on default error messages, or displaying unhelpful error messages (the error has a less helpful message than the response).getErrorMessage
andgetFormErrors
help with this.To be done
Problem
The frontend does not always display the error messages sent from the backend, and even when it does, it does not display the
detail
that is sometimes sent along with it.Definition of done for each ticket
displayError
in this XService. To replace the error snackbar, renderErrorSummary
in the relevant components with thedismissible
prop. This way, the user can expand the error detail if desired without the snackbar disappearing on them.getFormHelpers
in the relevant components; switch togetFormHelpersWithError
even if no error. (We will eventually rename it to replace the originalgetFormHelpers
.)assign
s the API error, rather than a hard-coded error message. If a hard-coded error message is needed as a fallback, send it as a prop toErrorSummary
.ErrorSummary
andgetFormHelpersWithError
.Tickets
The text was updated successfully, but these errors were encountered: