To be clear, I don’t have a lot of experience with JSON schema, but recently I found myself needing to validate Azure ARM templates using json schema, and my god is the Microsoft provided schema insane. Go look for yourself: https://schema.management.azure.com/schemas/2019-04-01/deplo...
That’s the root schema definition, but there are many, many references within, and they go deep. I tried using the bundling tool mentioned in the article to bundle all the references schemas and it came out to 25MB, minified. But if you don’t bundle, then you are right, your tool has to crawl the document and make many more http calls to deref everything. It’s so frustrating to work with.
I live within 15 miles of the main Microsoft campus in Redmond and only have access to shitty DSL. Microsoft has always taken the bet that everyone in the future will have access to high speed internet, but without ever raising a finger to make sure that future actually happens.
That depends on your definition of shitty ADSL. My old ADSL wasn't just slow, it was unstable and would regularly starting lagging out / having massive pings which would then go away and come back. Three years of talking to the ISP and I got nowhere. I now live in an NBN area and get Fibre to the Curb with 80MBPS down, I can now truly work from home.
That’s the root schema definition, but there are many, many references within, and they go deep. I tried using the bundling tool mentioned in the article to bundle all the references schemas and it came out to 25MB, minified. But if you don’t bundle, then you are right, your tool has to crawl the document and make many more http calls to deref everything. It’s so frustrating to work with.