TJ

As the title says, would just be nice for documentation to record the version which introduces a particular type, field, or method, not a huge priority though.

Would be nice to auto-generate a little example to show on https://pkg.go.dev/, might not be very useful since it's pretty self-explanatory, but at least show the `Client` initialization

We could potentially generate mock servers from any schema, as long as it has example responses defined then just return one of those at random. It could be a nice...

Not a big priority for me, but might be a nice option to generate CLIs, pretty much a 1:1 mapping, for example `logs add_project --name 'My Project' --description 'Production logs...

Right now it's something like `element 5: message is required`, might be nicer to use a json-path-ish thing like `events[5].message is required`. Some tests would also be nice haha

It would be great to generate Terraform providers, maybe not for all methods, but it could be opt-in per method.

Just add a comment so you can quickly see which version a client supports

Not a huge fan of the StatusProvider type stuff I have at the moment https://github.com/apex/rpc/blob/master/error.go#L7-L15, would be nice to also provide some functions for the common scenarios to keep them...

I need to look into inheriting from json-schema more, but I think we would then have to support everything JSON-Schema does — `oneOf` for example — but it would be...

This stuff I have now is kind of temporary, still need to decide what I want there, maybe opentracing support.