better error handling about asyncvoter-api HOT 3 OPEN

great suggestion from @krauszraphael

from asyncvoter-api.

I think this issue needs to be decomposed into various features.

For example, every controller function has a next parameter. We should either be a) handling the error in the controller; or b) passing it to the next method handle the error. By default, I believe we should be doing b. if (err) return next(err) (At least for the time being.)

Another example, we specify in Cucumber that a "sad path" returns an error. We should be going over the routes and defining what the return error codes (and for that matter success codes) writing the tests and implementing them.

from asyncvoter-api.

Additionally, if an error occurs on a certain API REST path, what HTTP error codes should we be returning and when.

from asyncvoter-api.