Went with a modal instead of toaster messages, but the same idea. Just an easy way to alert our users of errors from the backend.
Most errors, if possible, should be caught on the frontend, and in that spirit I set it up so names/descriptions have char counts everywhere and we don't let the user send names/descriptions (for creating bigbits/snipbits/stories and editing stories) if they are too short/long.
Aside from this, there aren't any places on the webapp that should trigger the error modal from a user mistake, at this point most of it should be if there is a bug in the API or something like that...
Snapshots
If I terminate the API while the frontend is running and refresh the page you can see the error modal in action
Closes
Closes #77
Description
Went with a modal instead of toaster messages, but the same idea. Just an easy way to alert our users of errors from the backend.
Most errors, if possible, should be caught on the frontend, and in that spirit I set it up so names/descriptions have char counts everywhere and we don't let the user send names/descriptions (for creating bigbits/snipbits/stories and editing stories) if they are too short/long.
Aside from this, there aren't any places on the webapp that should trigger the error modal from a user mistake, at this point most of it should be if there is a bug in the API or something like that...
Snapshots
If I terminate the API while the frontend is running and refresh the page you can see the error modal in action