ns1-go
ns1-go copied to clipboard
More verbose error output when encoutering a JSON decoding error.
Getting more information about what was actually sent to the client would be vital for understanding the fault itself in the event of a JSON decoding error.
This returns output explaining the response headers and response body of what was actually returned given an API call.
We initially tried to do this on our end, but since the request body was already closed in the ns1-go client, it is not possible to do this on the end-user side.
This has been fixed in PR #177 and is now available in release 2.7.2.