Call is always attempting to parse response body, which leads to errors in case
of no-response calls such as nameserver.deleteRecord.
In order to allow for such without breaking our API, let's:
rename the original Call into _Call
introduce a boolean of expectResponseBody into _Call
offer a new Call that keeps the stable interface, but translates into _Call(..., true)
offer a new CallNoResponseBody that can be used by such no-response calls
Then,
Use the new client.CallNoResponseBody instead of client.Call and avoid erroring
on body failing to parse in NameserverRecordUpdate & NameserverRecordDelete.
Call is always attempting to parse response body, which leads to errors in case of no-response calls such as nameserver.deleteRecord.
In order to allow for such without breaking our API, let's:
expectResponseBodyinto _CallThen,
Use the new
client.CallNoResponseBodyinstead of client.Call and avoid erroring on body failing to parse in NameserverRecordUpdate & NameserverRecordDelete.Fixes #12