Throws an error when "extensions and overlays" are undefined about raml-js-parser-2 HOT 5 CLOSED

What were the loadApi arguments?

from raml-js-parser-2.

Hm. Just tested, all those variants of the call do not throw an error for a valid API:

var parseResult = raml.loadApi(fName)

var parseResult = raml.loadApi(fName, {
    rejectOnErrors : true
})

var parseResult = raml.loadApi(fName, [fName2, fName3, fName4])

var parseResult = raml.loadApi(fName, [fName2, fName3, fName4], {
    rejectOnErrors : true
})

from raml-js-parser-2.

Undefined. raml.loadApi(path, includes, { rejectOnErrors: true }) but includes is undefined. I just worked around it by saying includes || [] but I'd expect null and undefined to be valid values - just as an empty array is.

from raml-js-parser-2.

We supported a whole syntax of raml.loadApi(path, { rejectOnErrors: true }) so that users do not have to put undefined as a second argument.

from raml-js-parser-2.

A actually agree with @blakeembrey.
pushed fix to RC2.

Regards,
Pavel

from raml-js-parser-2.