Let’s say that I have two json schemas:
and that foo-schema references types from common-schema using $ref.
If in my RAML file I have
schema: !include foo-schema.json
Then the foo-schema.json will be added to my API portal, but the dependent common-schema.json is not.
Is there any way to cause API designer to follow the schema references and include all files in the portal?