error handling on server for all modal calls

[JeffUberman]

front-end errors with duplicate ingredients/recipes

[mishasaggi]

running a migration on server start (handle below error)
Unhandled rejection Error: ENOENT, scandir '/Users/monisha/code/whatthefridge/migrations'
at Error (native)

[mishasaggi]

Error handling across features (turn off error displaying)

Errors that should be shown (a different page or modal?)
caused by users, like validation

Errors that should be hidden (should cause a delay, worst case)
if it can be handled by code, just log it
example database/server connections

Errors that should be shown as generic
example database connection refused. display generic error instead of actual the problem

[mishasaggi]

Error handling todos

errors to display to users (client side validation)

duplicate recipe name (toast it) for create recipe, edit recipe

any controller based error - log it. Not just the error but all variables being used by the method as well (all of http request), timestamp.

any http error - 400s, 500s - design the views with funny messages (rotates the message) for that and links to the dashboard.

on serious errors - send email/text to team/oncall person

[mishasaggi]

Use cases not covered by error handling:

Login - user not found, password incorrect