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
Some schemas, such as those for Credential Manifest rely on additional schemas using the $ref property.
Utilizing these schemas in the sdk resolves in network calls, to resolve the $ref values. It's possible some of these schema URIs may become unavailable. We should have a method to "locally" resolve such schema references. This is possible in ajv.
The text was updated successfully, but these errors were encountered:
// DerefSchemas takes our known schemas and dereferences the schema's $ref http links to be a part of the json schema object.
// This makes our code faster when doing validation checks and allows us to not ping outside sources for schemas refs which may go down or change.
// TODO: (Neal) Currently we do not use these dereferenced schemas in code because there is more work to be done here.
// Currently these dereferenced schemas are missing some information and fail validation with our known json objects
// I believe some more work in the investigation library needs to be done and we need to handle circular dependencies
it could also be our logic to do validation is strange, it seems that these schemas + json objects with an online tool check out..
Some schemas, such as those for Credential Manifest rely on additional schemas using the
$ref
property.Utilizing these schemas in the sdk resolves in network calls, to resolve the
$ref
values. It's possible some of these schema URIs may become unavailable. We should have a method to "locally" resolve such schema references. This is possible in ajv.The text was updated successfully, but these errors were encountered: