Access SchemaRegistry about jayschema HOT 4 CLOSED

@pvorb What would be the use case? I can see the case for isRegistered(id), but get(id) is harder to understand: you added the schema, so why do you need to retrieve it?

If there’s a good use case for this, ultimately the SchemaRegistry object itself may need to be exposed. Maybe you’d be able to pass a SchemaRegistry to the Validator constructor; the Validator would create a default SchemaRegistry if none was passed.

from jayschema.

I am working with a lot of (20+) schema files that are all traversed once and then registered with JaySchema. Afterwards I want to validate even more data. validate() needs a “main” schema to validate an instance, so I either would have to reload the schema from disk or hold another data structure that maps from IDs to schemas.

If I could retrieve the schema from JaySchema's registry, I wouldn't need that additional data structure. But it's your decision. If you think the registry should be hidden from the user, that's ok.

from jayschema.

Ah, I see. I recently added a feature where you can pass a string id to the validate() function instead of a schema. So you shouldn’t need to get hold of the schema again if you know its id.

Does that solve your problem?

I do think it makes sense to expose isRegistered(id). That can be helpful if you’re registering a whole bunch of schemas.

from jayschema.

Ah, I see. I recently added a feature where you can pass a string id to the validate() function instead of a schema.
So you shouldn’t need to get hold of the schema again if you know its id.

That's exactly what I need. :-) I must have missed this feature.

from jayschema.