{"id":2695,"date":"2018-11-01T16:55:31","date_gmt":"2018-11-01T14:55:31","guid":{"rendered":"http:\/\/hasselba.ch\/blog\/?p=2695"},"modified":"2018-11-01T17:00:28","modified_gmt":"2018-11-01T15:00:28","slug":"node-js-domino-db-docker-4-error-handling","status":"publish","type":"post","link":"https:\/\/hasselba.ch\/blog\/?p=2695","title":{"rendered":"node.js, domino-db & Docker (4): Error Handling"},"content":{"rendered":"

When we started our express application and accessed it in the browser, an error raised on the console and no response was sent back to the browser. The reason for this behaviour is that the database connection is not correctly configured, and the request from our application fails.<\/p>\n

For a better understanding I have refactored the code to „old-school“ Javascript. The functions are called in a promise<\/a> chain.<\/p>\n

router.get('\/', function(req, res, next) {\r\n  useServer(serverConfig)\r\n  .then(\r\n      function(server){\r\n        return server.useDatabase(databaseConfig)\r\n      })\r\n  .then(\r\n      function(database){\r\n        return database.bulkCreateDocuments(createOptions)\r\n      })\r\n  .then(\r\n      function(response){\r\n        const unids = response.documents.map(doc => doc['@unid']);\r\n        res.render('index', { title: 'Express', result: `Documents created: ${unids}` });\r\n      }\r\n  );\r\n});<\/code><\/pre>\n
1. The get<\/em> method of the router<\/em> calls the anonymous function (2nd parameter).<\/p>\n
2. The chain starts: This function calls the useServer<\/em> method of the domino-db package with the serverConfig<\/em>.<\/p>\n
3. If everything is OK, the next method in the chain is called with the server<\/em> object (the result of the previous operation).<\/p>\n
4. If everything is OK, the next method in the chain is called with the database<\/em> object.<\/p>\n
5. If everything is OK, the next method in the chain is called with the result<\/em> object.<\/p>\n
Promises have two callback functions: The first parameter is always the „success“ callback, and the second the „error“ callback. But we are not using a second parameter, because this allows us to use a catch<\/em> function at the end of our chain:<\/p>\n
router.get('\/', function(req, res, next) {\r\n  useServer(serverConfig)\r\n  .then(\r\n      ... )\r\n  .then(\r\n      ... )\r\n  .then(\r\n      ... )\r\n  .catch(\r\n    function(error) {\r\n      console.log(error);\r\n      res.render('error', { title: 'Error', error });\r\n    }\r\n  );\r\n});<\/code><\/pre>\n
The catch block handles every error in our chain, and renders the view ‚error<\/em>‚ with the reason of the failure.<\/p>\n
If we now restart our application, the error is displayed to the end user with a stacktrace:<\/p>\n
\"\"<\/a><\/p>\n
And now, we are refactoring the code using the arrow syntax<\/a>:<\/p>\n
router.get('\/', (req, res) => {\r\n  useServer(serverConfig)\r\n  .then(server => server.useDatabase(databaseConfig))\r\n  .then(database => database.bulkCreateDocuments(createOptions))\r\n  .then(response => {\r\n        const unids = response.documents.map(doc => doc['@unid']);\r\n        res.render('index', { title: 'Express', result: `Documents created: ${unids}` });\r\n  })\r\n  .catch(error => {\r\n      console.log(error);\r\n      res.render('error', { title: 'Error', error });\r\n    }\r\n  );\r\n});<\/code><\/pre>\n
A lot shorter, isn’t it?<\/p>\n
At the end, we are using async\/await<\/a> syntax to shorten the promise chain too:<\/p>\n
router.get('\/', (req, res) => {\r\n  useServer(serverConfig).then(\r\n    async server => {\r\n      const database = await server.useDatabase(databaseConfig);\r\n      const response = await database.bulkCreateDocuments(createOptions);\r\n      const unids = response.documents.map(doc => doc['@unid']);\r\n      res.render('index', { title: 'Express', result: `Documents created: ${unids}` });\r\n    }\r\n  ).catch(error => {\r\n      console.log(error);\r\n      res.render('error', { title: 'Error', error });\r\n  });\r\n});<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"
When we started our express application and accessed it in the browser, an error raised on the console and no response was sent back to the browser. The reason for this behaviour is that the database connection is not correctly … Weiterlesen →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9,134,131],"tags":[7,138,133,135,132],"class_list":["post-2695","post","type-post","status-publish","format-standard","hentry","category-javascript","category-jsx","category-node-js","tag-domino","tag-domino-db","tag-express","tag-jsx","tag-node-js"],"_links":{"self":[{"href":"https:\/\/hasselba.ch\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2695","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hasselba.ch\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hasselba.ch\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hasselba.ch\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/hasselba.ch\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2695"}],"version-history":[{"count":4,"href":"https:\/\/hasselba.ch\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2695\/revisions"}],"predecessor-version":[{"id":2701,"href":"https:\/\/hasselba.ch\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2695\/revisions\/2701"}],"wp:attachment":[{"href":"https:\/\/hasselba.ch\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2695"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hasselba.ch\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2695"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hasselba.ch\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2695"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}