Skip to main content

Generate C# code from a JSON schema - Part I

I’m having fun creating a small open-source project(more about that later). In a part of this project I need to integrate with an existing API. I first started by browsing through the API documentation and use that to build my data contract classes in C# until I discovered that a JSON schema document was provided.

In this post I want to show you can use this JSON schema document to generate the C# classes instead of writing them from scratch

JSON schema

Before I show you how to generate the C# code, I want to take a small detour and give you some more details about JSON schema itself.

Let’s have a look how it is explained on the json-schema.org website itself:

JSON Schema is a vocabulary that allows you to annotate and validate JSON documents.

If you have ever used SOAP services in a previous life, JSON Schema can be compared to the WSDL documentation that was available there.

It gives you an concise and easy way to describe your data format, provides you all the metadata to generate your data contract and allows you to test and validate submitted data.

Here is an example I copied from the json-schema.org website:

Generate C# data contracts using Quicktype

I first decided to give Quicktype a try. The website mentions:

Instantly generate C# models and helper methods from JSON

Sounds exactly like what I needed.

I opened the Quicktype application here.

I changed the Source type to ‘JSON Schema’.

I pasted my target schema and immediately the related C# models where generated. Nice!

The only disadvantage of Quicktype is that is still using Newtonsoft.Json where I typically use System.Text.Json nowadays.

Tomorrow I’ll have a look if I can find an alternative that supports System.Text.Json…

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.