Hey folks,

I noticed in our TO go client that we aren't decoding the JSON
response returned from PUT/POST endpoints. If we actually decoded
those responses, it would be quicker and more useful from a user's
perspective, save bandwidth from all the unnecessary GETs after
POST/PUTs, and also reduce load on the API server.

Is there a reason why we don't decode those responses?

- Rawlin

Reply via email to