err, errors not nil about go-client HOT 3 CLOSED

@markschmid thanks for being invested enough to share your findings with us as we're working through this new client. I've updated the client-builder and regenerated the go-client with the suggested behavior. Thanks!

from go-client.

Great, thanks @matthew-altman ! For successful calls I'm getting now getting nil for errors and err.

E.g. for a call that results in 404 err and errors are still non-nil (EOF and &{map[] []} respectively). I suppose that's intended.

For errors, I can additionally check for empty struct/map besides nil, no problem. For err, can I assume EOF bears the same meaning nil in those cases?

from go-client.

@markschmid since there are lots of different reasons for failures there would probably be a lot of conditional checks that I could do to determine if/when to populate the err and errors. In your most recent example the err is probably returning an EOF since we're attempting to load the errors object with the response for a non successful call. However, a 404 wouldn't return validation errors. This is perhaps something we can address in a future iteration.

from go-client.