Repository navigation
How to migrate from RefResolver to referencing #1079
Description
Trying to follow https://python-jsonschema.readthedocs.io/en/latest/referencing/#migrating-from-refresolver using the latest alpha version but I can't get it to work. I currently have
def get_schema():
return {
{
"$schema": "http://json-schema.org/draft-04/schema#",
"definitions": {
"edm": {...},
"eem": {...}
},
"anyOf": [
{
"$ref": "#/definitions/eem/events/SISAddress"
},
{
"$ref": "#/definitions/eem/events/SISEnrollment"
},
{
"$ref": "#/definitions/eem/events/SISPerson"
},
{
"$ref": "#/definitions/eem/events/SISRestriction"
},
{
"$ref": "#/definitions/eem/events/SISSection"
}
]
}
}
my_schema = get_schema()
schemastore = {
'https://my_url/EDM.json': my_schema['definitions']['edm'],
'https://my_url/EEM.json': my_schema['definitions']['eem']
}
resolver = jsonschema.RefResolver(base_uri='', referrer=my_schema, store=schemastore)
jsonschema.validate(payload, my_schema, resolver=resolver)
I tried to do
my_schema = get_schema()
schema = Resource.from_contents(my_schema)
registry = Registry().with_resources([
('https://my_url/EDM.json', my_schema['definitions']['edm']),
('https://my_url/EEM.json', my_schema['definitions']['eem'])
])
validator = Draft4Validator(schema=my_schema, registry=registry)
validator.validate(payload)
but I get
...
File ~/.virtualenvs/sds/lib/python3.10/site-packages/referencing/_core.py:394, in Registry.crawl(self)
391 while uncrawled:
392 uri, resource = uncrawled.pop()
--> 394 id = resource.id()
395 if id is not None:
396 uri = urljoin(uri, id)
AttributeError: 'dict' object has no attribute 'id'
Activity
Julian commentedon Apr 5, 2023
You're passing
dicts (object schemas) to the second argument ofwith_resources, but it takesreferencing.Resourceobjects, which are essentially your dict wrapped with the information that it is a Draft 4 schema.You could instead either call
Resource.from_contentson your dicts if they contain$schemakeys, or usereferencing.jsonschema.DRAFT4.create_resource(each)on them to explicitly say they're draft 4 resources, or even better would be if they haveidkeys in them indicating they're subresources (so e.g."id": "https://my_url/EDM.json"in yourdefinitions/edmschema) in which case you need to do nothing extra at all, they'll be automatically found if your parent schema resource is in the registry.Hope that helps but if there's suggestions for how you'd have figured the above out in the doc page you linked let me know.