René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Provide error code when a function call has failed","articleBody":"```JavaScript\r\nreturn git.Merge.base(repo, parents[0], parents[1]);\r\n.then(function(ancestor) {\r\n  console.log(ancestor);\r\n})\r\n.catch(function(err) {\r\n  console.log(err);\r\n})\r\n```\r\nRunning the code above will print out the output below if the two commits have no common ancestor.\r\n\r\n```[Error: No merge base found]```\r\n\r\nThe error code behind this error is `Error.CODE.ENOTFOUND` but there is no way for a client to know this. Not having a common ancestor between two commits is an error that a client may be able to handle gracefully but if it the function failed because of some other fatal error then maybe the client can't do anything about it. Without an error code available in the `catch` callback, clients have no way of figuring out why the function failed outside of parsing the error message itself. It would be nice if we could have something like either of the two following patterns...\r\n\r\n```JavaScript\r\ncatch(function(err, code) {\r\n  console.log(err);\r\n  console.log(code);\r\n});\r\n```\r\n```JavaScript\r\ncatch(function(err) {\r\n  console.log(err.msg);\r\n  console.log(err.code);\r\n});\r\n```","author":{"url":"https://github.com/rcjsuen","@type":"Person","name":"rcjsuen"},"datePublished":"2017-01-29T04:53:25.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/1206/nodegit/issues/1206"}