Document how to pre-populate the catalog more clearly about jschon HOT 3 CLOSED

Another wrinkle is that usually when I use this source I don't care about associating it with a base URI — I just want it to work for everything, which is not supported by the current Source interface. And having an InMemorySource like this essentially serves as a manually populated cache for the catalog's automatically managed cache. So perhaps a public interface to load schemas directly into the catalog would be a better option? This would be distinct from Catalog.add_schema(). [EDIT: Or if it's Ok for end users to use Catalog.add_schema() I could just make a documentation/tutorial PR about that?]

I'm not sure what the best design is here, I just know that it's my most common use case and feels like it involves too much boilerplate for something that's technically even more straightforward than the two supported sources.

from jschon.

OK so in the end all that happened here is that I assumed that since there was a tutorial for reference resolution that talked about Sources, that I needed a source even for an in-memory thing.

Of course this is not true, just instantiating a JSONSchema object caches it in the relevant catalog. I'll look at the documentation and see if I think there's a way to make this a bit more clear for the workflow of pre-populating the catalog with all relevant schemas.

As usual with jshcon, in the end there is much less of a problem and a much easier solution than I initially feared. 😅 😁

from jschon.

...and I still don't know what I'm talking about. I'm going to close this, and when I'm absolutely sure I know what I mean I will file an issue grounded in actual use cases and passing/failing tests.

from jschon.