JSON-to-Go VS go-cmp

That site likely uses Matt's lib for that functionality: https://github.com/mholt/json-to-go

https://mholt.github.io/json-to-go/ is a nice tool for generating a struct definition to fit some sample JSON.

json-to-go is your friend.

JSON to struct. I use this about 100 times a day, no joke.

https://mholt.github.io/json-to-go/

Do your best to get static types on everything. Play a game with yourself where interface{} is banned and try to do your work. One of the most common sources of such loosely-typed values in JSON, so I'll point out this automatic struct generator for instance. If you have questions about a specific place you don't see how to avoid interface, feel free to ask. Every once in a while I do have to reach for something like this, but it should be rare.

But given we know ChatGPT can't accurately generate structs from even moderately complex json objects why bother doing all of that legwork of verifying and chiding chatgpt, when you can just drop it into a tool like https://mholt.github.io/json-to-go/ and get a correct struct in a fraction of the time?

I use https://marketplace.visualstudio.com/items?itemName=maracko.json-to-go, which is an extension version of https://mholt.github.io/json-to-go/

I think using struct in such cases is almost always the right approach. There are tools which generates go structs from json this.

This made me think of a couple other interesting things:

1. you can change which algorithm is used in git diff as multiple are supported

https://luppeng.wordpress.com/2020/10/10/when-to-use-each-of...

2. Google has an edit graph implementation in Go in the cmp package

https://github.com/google/go-cmp/blob/master/cmp/internal/di...

Assertion libraries that people seem to love: - testify (my favorite) - go-cmp is a more barebones library - gotest.tools -- I have never used this but some swear by it

it uses https://github.com/google/go-cmp instead of reflect.DeepEqual

When I use functional arguments, I either prefix all of the options with the same prefix or put them in a dedicated package (like cmpopts) to help the IDE.

Checking for equality in tests: https://github.com/google/go-cmp

oklog/ulid to generate IDs. coreos/go-oidc for validating JWTs I get from auth. google/go-cmp for comparing structs in tests (unless the project is already using Testify). spf13/pflag because life's too short for Go's flag handling. getkin/kin-openapi for validating reqests/responses against my OpenAPI spec (in tests).

One thing to keep in mind about reflect.DeepEqual is because of the way it is implemented you could get positive results when the values are not actually the same, see this comment for reference.