jsonschema | draft 2020-12 , draft | JSON Processing library

If you put all the mappers/parsers in a map you won't have to use switch case statements. And things will be easier to implement:

Where I get confused is that in order to load my schemas before I've published them (which I want to do while running tests locally and during CI/CD), I need to use relative local paths

Your initial assumption is false. URIs used in the $id keyword can be arbitrary identifiers -- they do not need to be resolvable via the network or disk at the stated location. In fact, it is an error for a JSON Schema implementation to assume to find schema documents at the stated location: they MUST support being able to load documents locally and associate them with the stated identifier:

The "$id" keyword identifies a schema resource with its canonical URI.

Note that this URI is an identifier and not necessarily a network locator. In the case of a network-addressable URL, a schema need not be downloadable from its canonical URI.

source

A schema need not be downloadable from the address if it is a network-addressable URL, and implementations SHOULD NOT assume they should perform a network operation when they encounter a network-addressable URI.

source

Therefore, you can give your schema document any identifier you like, such as the URI you anticipate using when you eventually publish your schema for public consumption, and perform local testing using that identifier.

Any implementation that does not support doing this is in violation of the specification, and this should be reported to its maintainers as a bug.

So I found the answer, also thanks to @prasad_ comment: The problem was a syntax error here are the bad and good version side to side :

The error says that either you haven't got Django installed or didn't activate the virtual environment in which the Django was installed. Make sure that you check the list of installed packages and find Django in there, via:

This is weird behavior maybe caused by the provider knowing the result of the resource fields beforehand and confusing terraforms implicit dependency detection.

You can try to force the dependency by adding an explicit depends_on to the iam resource to ensure recreation:

I think you might want to be using the oneOf construct. Basically, you're trying to describe a list that can contain any number of two different kinds of objects.

Here's an example of use:

A recursive algorithm suits this.

I divided it into 2 different functions as removing undefined properties and filling non-existent ones from the schema are 2 different tasks. You can merge them into one if you wish.

For filling nonexistent properties, I just create arrays, objects and Nones, and then recurse inwards.

For removing the undefined properties, I compare the schema keys and remove unmatched keys, again, recursing inwards.

You may see comments and type checks in code:

Consider creating a separate environment, e.g.,

You can use a schema validator for validating schemas. There are special schemas called meta-schemas, that validate other "normal" schemas (and themself). For the json schema specification, you can download such meta-schemas from the specification webpage.

There you can download the "Core/Validation Dialect meta-schema". You then can validate any other json schema with