Frontend Success and Error Handling

Success Messages Only if Clear Signal for Success

We only show a success message when there is a clear signal to do so.
Avoid “assumptive” success messages unless very clear reason.
A request does not need to show a success message by default.
If it does show one it must have a high degree of correctness.

Example:
Showing success on 200 OK is good.
Showing success because another process completed is bad because it assumes success when in fact that process may have failed.

Failure Messages Required

A request must propagate errors to the UI unless there is a clear reason not to.
We will reject any pull requests that don’t satisfy this.

Example:
Good: Catching error and passing to regular error component.
Bad: Doing nothing with error or throwing it to console log.