Jim Blackler

Hi @DVanderstoken could you elaborate at all?

I would consider it but it'll have to go on the to do list because I've a bit of a backlog and haven't uploaded anything there before.

Interesting idea. Next round of development I'll try it. On 21 Nov 2015 05:04, "Olathe" [email protected] wrote: > Could you perhaps change the youtu.be links to use HTTPS? This will...

I tested it this way and it worked: ```json { "$defs": { "tree": { "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "https://example.com/tree", "$dynamicAnchor": "node", "type": "object", "properties": { "data": true, "children": { "type": "array",...

Step one is to not NPE if $dynamicAnchor doesn't resolve, which is obviously bad. https://github.com/jimblackler/jsonschemafriend/commit/c2d871f19a3e83a24fdbf5ff6a3b195e0c586e0a It doesn't fix your test case though so I'll look more into that.

OK the issue is the port spec in the URL http://localhost:1234/strict-tree.json. The library was mishandling those. https://github.com/jimblackler/jsonschemafriend/commit/e5d884a8499c820313767cc492f5e0463c0c8559 contains fixes for this specific test case (although it's possible there are more).

They can be cached on the first instance if you ever do have internet access. It's not strictly necessary to have the metaschema, it just can't validate the schemas themselves....

Depending on how you load the schemas, providing 'null' as the validator https://github.com/jimblackler/jsonschemafriend/blob/e2e33667772ff13ad8876c39b61b2deb32590118/library/src/main/java/net/jimblackler/jsonschemafriend/SchemaStore.java#L72 should cause the metaschema not to be loaded. Can you try that?

Sorry I thought I had made a release since then. I'll do a release when the current outstanding PR is in.

Thank you for the reminder. I just pushed 0.11.3, it should show up on Jitpack shortly.