Errors/exceptions in load handler are swallowed without trace about raml-js-parser HOT 2 CLOSED

Hi @mgurov, that is effectively how promises work. When an exception is thrown in a promise body, the whole promise is rejected with the error as argument. Since the exception is handled by the Promise (in this case we are using the q module, your event for unhandled exception will not get fired.

This is how you should catch errors in your code (I am using your first snippet as base):

var raml = require('raml-parser');

var definition = [
    '#%RAML 0.8',
    '---',
    'title: MyApi',
    'baseUri: http://myapi.com',
    '/Root:'
].join('\n');

raml.load(definition).then(function (data) {
    throw "Did something wrong in handling";
})
.catch(function (error) {
    console.log('Error parsing: ' + error);
});

I will be closing this issue.

from raml-js-parser.

Hi @dmartinezg,

Thank you for the quick reply. Yes, the catch of the q promise worked OK for me, no issue.

I used to have some experience with promises before, via angular.js, but the catch there is a shorthand to promise.then(null, errorCallback) (see https://docs.angularjs.org/api/ng/service/$q#the-promise-api ). Hence the confusion. Maybe adding a pointer to q to the top level documentation would save time next time.

from raml-js-parser.