Restricting the compilation of Includes in RAML about raml-js-parser HOT 3 CLOSED

Hi @priyavivek1, the parser processes a lot of the content, and resolves schemas names to schema content.

There is a feature flag not to resolve schema names, you can disable schema transformation like this: https://github.com/raml-org/raml-js-parser/blob/master/test/specs/schemas.js#L124

from raml-js-parser.

Thanks @dmartinezg, it worked for me in latest version : Is there any feature to restrict the schema compilation at root level also.
For eg

schemas:
RetrievePartyAlternatePartyKeyListRs: !include jsd/RetrievePartyAlternatePartyKeyListRs.1.schema.json

raml.loadFile(source, {applySchemas: false}).then(function(data) {
console.log(data.schemas)
}

when i print data.schemas, it gives me compiled schemas as below
{"RetrievePartyAlternatePartyKeyListRs" : "compiled schemas"}

from raml-js-parser.

No, there is no way to disable resolution of !include tags, and I wonder if it is legal RAML 0.8, the spec says:

When RAML or YAML files are included, RAML parsers MUST not only read the content,
but parse it and add the content to the declaring structure as if the content were declared inline.

from raml-js-parser.