Open ChetanBhasin opened 7 years ago
Doing that would imply disabling certain consistency checks in the RAML definition and json-schema files. I'll keep your suggestion in mind and see if we can find an elegant solution for this. Since our work on integrating RAML 1.0 is lagging behind a bit, RAML 1.0 will stay the first priority for now.
I came across an interesting use case in which a project Y depends on the code and schemas from project X. So if I want to reference schemas in JSON or YAML from project X in project Y then I must have all the files in one place and reference them via IDs and put them in my RAML file.
It would be immensely useful to be able to reference classes that are pulled from the SBT/Maven dependency and do not have their schemas in YAML or JSON referenced from the project.