Matthew Adams
Matthew Adams
I would suggest creating a [JSON Schema](https://json-schema.org) to define the spec. Here's a first pass at that. ```json { "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "https://github.com/obsidianmd/jsoncanvas/canvas.json", "title": "An open file format for infinite...
As far as I can tell, the spec doesn't define the coordinate system in use (e.g. which direction is positive in each axis, what point on the entity is represented...
An issue was opened against my json-schema implementation https://github.com/corvus-dotnet/Corvus.JsonSchema/issues/238 This turned out to be an implementation-specific bug that related to the handling of references to non-keyword schema islands. While this...
We have a very basic `ISpanFormattable` implementation on all string types so that they can participate in interpolated string formatting without allocating strings on net8.0 and above. We should provide...
If a schema supports one of the common string formats, then it would be useful to support conversions to the relevant concrete string format types (e.g. `JsonUriTemplate`, `JsonUuid`). At the...
We would like to be able to convert our validation context results into the standard [JSON Schema output format](https://json-schema.org/draft/2020-12/output/schema).
The enum keyword itself doesn't support documentation. The recommended method for "documenting" your enum-like values is to use the `oneOf` keyword: ```json "oneOf": [ { "const": "some value", "title": "Some...
Create a command line tool to take a schema and run validation against a given JSON document.
We would like to be able to emit an assembly from the command line tool in addition to the raw C# code. This might be a friendlier path for non-C#...