JSON to Go

Go structs need a tag on every field to map it to a JSON key, which makes writing them by hand for a large payload slow. This produces the full set, formatted the way gofmt would align them.

Exported names follow Go conventions, including the initialisms the linter expects: an id key becomes ID, not Id.

Why are some fields pointers?

Optional fields become pointers tagged omitempty, which is the only way encoding/json can tell a field that was absent from one that arrived as the zero value. Without it, a missing count and a count of 0 are indistinguishable.

Why interface{} instead of any?

any is an alias for interface{} added in Go 1.18, so the two are identical to the compiler. The output uses interface{} because it also compiles on older toolchains, and a struct definition is the last place you want a build to break over a spelling.

How are optional fields decided?

Every record in an array is inspected, not just the first. A field that appears in some records and not others is typed as optional, and a value that is sometimes null widens accordingly. Generators that read only the first element get this wrong on exactly the payloads where it matters.

What happens to a key that is a reserved word?

It is renamed to something legal in the target language, and where the language supports it, an annotation records the original JSON key so serialisation still round-trips.