commit 10c31def2583536d29febd33330bb8099750896d
author Kamil Musin <kamilm@google.com> Thu Feb 08 16:49:38 2024 +0100
committer Kamil Musin <kamilm@google.com> Wed Feb 28 13:35:48 2024 +0100
tree d615962ecc1f155c00a75adef4c61ca332c7b099
parent 3e239515f3deb1774fd288f7fdf775fe5808729c

Replace send method usage

Send is largely a duplicate of the logic that is found in fetch and
fetchJSON, but combines both parsed and naked Response logic and has
slightly different error handling. To avoid confusion and reduce
duplication we remove send() method and replace it with fetch or
fetchJSON depending on whether response needs to be parsed or not.

The difference between send() and fetch() is behaviour when receiving
non-200 error code. send() will show an error message with an error,
while fetch returns response as-is to be parsed by the caller. To
account for this we set reportServerError to true for all calls to
fetch. fetchJSON() has the same server-error handling as send, so that
is not needed, in cases where `parseResponse: true`.

Some methods have wrong return types: don't account for the fact that
response can be undefined if parsing is required. We fix the return type
annotation and additionally fix callsites, if they don't properly handle
the null value.

AddAccountSSHKey and AddAccountGPGKey similarly were reimplementing
logic of fetchJSON, so instead we pass throwingErrorCallback to achieve
the same result.

Google-Bug-Id: b/297849592
Release-Notes: skip
Change-Id: I8e636a1423d950c0b3e9e64b8b61a20c8342764f