thereadme/hapi-sequelize-crud
1
0
Fork 0
Code Issues 4 Pull Requests 1 Projects Releases Wiki Activity

Fix a bug in error parsing #21

Merged
joeybaker merged 3 commits from better-error into master 2016-09-05 19:25:14 +00:00
Conversation 4 Commits 3 Files Changed 1 +24 -10
1 changed files with 24 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
src/error.js
View File

@ -8,11 +8,20 @@ export default (target, key, descriptor) => {
await fn(request, reply);
} catch (e) {
if (e.original) {
const { code, detail } = e.original;
const { code, detail, hint } = e.original;
let error;
// pg error codes https://www.postgresql.org/docs/9.5/static/errcodes-appendix.html
if (code && (code.startsWith('22') || code.startsWith('23'))) {
const error = Boom.wrap(e, 406);
error = Boom.wrap(e, 406);
} else if (code && (code.startsWith('42'))) {
error = Boom.wrap(e, 422);
// TODO: we could get better at parse postgres error codes
} else {
// use a 502 error code since the issue is upstream with postgres, not
// this server
error = Boom.wrap(e, 502);
}
// detail tends to be more specific information. So, if we have it, use.
if (detail) {
@ -20,8 +29,13 @@ export default (target, key, descriptor) => {
error.reformat();
}
reply(error);
// hint might provide useful information about how to fix the problem
if (hint) {
error.message += ` Hint: ${hint}`;
error.reformat();
}
reply(error);
} else if (!e.isBoom) {
const { message } = e;
let err;