SJRK-356: Display meaningful error messages from backend errors

Metadata

Source
SJRK-356
Type
Task
Priority
Major
Status
Open
Resolution
N/A
Assignee
N/A
Reporter
Giovanni Tirloni
Created
2020-05-06T16:52:35.340-0400
Updated
2020-05-06T16:54:55.648-0400
Versions
N/A
Fixed Versions
N/A
Component
N/A

Description

When the /stories endpoint reports an error (e.g. HTTP 500 coming from a database down situation), the UI currently displays a blank page without information.

It'd be interesting to surface an error message to the user so they are not stuck wondering what is happening.