You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.
Proposal: Externals should be allowed in a union if they are not extended or mixed with internals.
#%RAML 1.0
---
types:
A:
type: !include A.schema.jsonB:
type: !include B.schema.jsontitle: externals with unionbaseUri: https://example.com/resource:
post:
body:
application/json:
type: A | B
The above currently receives the following error message:
EXTERNALS_MIX: It is not allowed to mix RAML types with externals
If I alter the above example to use RAML types instead of JSON Schemas, the union works as expected; however, I lose the benefits of extracting and using JSON schemas.
It's also important to note that I'm using raml2html to validate my RAML document.
Would the community be open to allowing this behavior?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Proposal: Externals should be allowed in a union if they are not extended or mixed with internals.
The above currently receives the following error message:
If I alter the above example to use RAML types instead of JSON Schemas, the union works as expected; however, I lose the benefits of extracting and using JSON schemas.
It's also important to note that I'm using raml2html to validate my RAML document.
Would the community be open to allowing this behavior?
The text was updated successfully, but these errors were encountered: