Sorry for my mistake, I think anchors was references to other files, not YAML anchors So there is no problem with the spec.
To parse these files, I uses raml-1-parser with
expand(true) methods with a small API like:
If I have all the includes inside the typesLib.raml (as the previous example code) the raml-1-parser only returns the
t.OtherTestType, nothing about TestType.
But, if I use a modified version of the typesLib.raml (the same file replacing the
!include ... with the file content):
#%RAML 1.0 Library
the parser returns both object inside the types properties, TestType and OtherTestType, which I think is the expected output (with these JSON I could execute other tools like datatype expansion).
I could take a look inside the raml-1-parser and try to fix the problem in the
Thanks for your answer and sorry again for my mistake!!!