We've just published a series of 17 (!) posts on common patterns in JSON Schema; lots of these have been culled from questions asked in the JSON-Schema Slack channel.
They are written from the perspective of .NET developers who are used to JSON serialization as a code-first exercise, and want to migrate towards schema-first (with generated code examples from Corvus.JsonSchema).
Some new features in Corvus.JsonSchema - our low-allocation, high-performance #JsonSchema serialization & validation library for #dotnet.
V3.0.10 brings support for arrays of rank >= 1, including C#12 collection expression initializers, and the ability to set values deep within an array of rank > 1.
We detect fixed-size numeric arrays of any rank, and allow you to convert to- and from-Span<T> for use in vectorized APIs such as System.Numerics.TensorPrimitives.
Does anyone know if @tailscale has published a schema for their ACL file anywhere? The docs are fine but aren't (really) machine readable, so translating them into #CUE or #JSONSchema will be a manual process that's boring to repeat as the docs evolve and features are added. Got any ideas? #tailscale
#python people: I want to build a package that is based on the new pydantic. It should feature click cli and typer cli generation from pydantic models jsonschema, api cli generation from openapi spec and form generation for html using jsonschema. Who is in?
One building block that allows me having forms in the terminal (and later in the web) I just built. Now my data models get more power! My tests generate code when I change models, my registries tell me what models are capable of and a smart task runner should follow soon.
Exposed all JSON serializers for public types. This was required to support JSON source generation in client code. No functionality updates, though, so if you're not using source gen, you can skip this one!
This has a number of updates, the most significant of which is stable ordering of property names in e.g. Create() methods.
While this is not technically a breaking change, because the ordering was unstable before, it is more-or-less guaranteed to break your code if you relied on property ordering rather than naming.
Recommendation: explicitly specify your parameter names on calls to Create() before you regenerate.