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
If a schema is being referenced via $ref and that reference cannot be resolved within the schema itself or from one of the schemas passed into the schemas property of the options, this needs to be indicated. A reasonable default would be to throw an error, but it would also be appropriate to indicate this issue at validation-time (as done in #46).
This would help take care of some of the issues referenced in #22.
The text was updated successfully, but these errors were encountered:
It seems like the compilation-time error-throwing is present on the validation libraries that are closer in interface to this library, so it could be the least-surprising solution. Additionally, since the main schema and all possible remotes are given at the same time, we don't need to worry about the possibility of a referenced schema being supplied later.
1 at what point unresolved reference errors are indicated 2 interface used to add remote schema references 3 interface that allows 'registering' remote schemas using a method, e.g. in Z-Schema: validator.setRemoteReference(requiredUrl, JSON.parse(body)); 4 interface like in imjv, where remote schemas are provided at the same time as the main schema to validate against
If a schema is being referenced via
$ref
and that reference cannot be resolved within the schema itself or from one of the schemas passed into theschemas
property of the options, this needs to be indicated. A reasonable default would be to throw an error, but it would also be appropriate to indicate this issue at validation-time (as done in #46).This would help take care of some of the issues referenced in #22.
The text was updated successfully, but these errors were encountered: