Greg Dennis

Hm... I could have sworn I implemented a serializer for `JsonValue`-typed values. You can implement an `ISerializer` yourself and register it. Instructions are here. Unfortunately, I don't have time to...

Yeah. Those are the instructions. Meant to link to the rendered site, but that'll do.

The `JsonSchema` type won't deserialize properly if the data doesn't match the expected model. I look at that as a benefit of being in a strongly-typed language. If you want...

> as the "type": "array" does not have the required "items" I see what you're saying. `properties` only pertains to object values and when a schema specifies that the type...

A Json.Net implementation has been found: https://github.com/yavuztor/JsonLogic.Net. It hides the model, which is my main argument agains Json.Net, so at least it's consistent.

Firstly, thank you for the suggestion. Before we get to it, I'd like to clarify that `additionalProperties: true` in JSON Schema is implicit. JSON Schema will not fail an instance...

> I'm also thinking about a refiner that add required for all non-nullable properties as well, but I have not yet tried. There is already some provision for this. Please...

> there isn't a way to say that all fields should be required in the schema This is also true about JSON Schema, which this library is modelled after. I...

> How is that better than the current situation of manually maintaining the json schema? Even with the copies, you still get the advantage of the compiler, especially if you...

I think this may actually be a good extension to the Patch library. It could analyze the differences and generate JSON Patch documents that represent the transformation from one to...