Repository navigation
Return raw response object for all API calls #434
Description
Activity
I like
apiResponsefor it's unmistakable clarity.apiResponseit is!Should this be thebody(json parsed object) or raw string response?Going to do
body, makes most sense. Just don't know what we should do for datastore which has a protobuf response type AFAIK.- added a commit that references this issue
on Sep 15, 2022 16 remaining items
- added a commit that references this issue
on Feb 2, 2026 - added a commit that references this issue
on Feb 3, 2026 - added a commit that references this issue
on Feb 3, 2026 - added a commit that references this issue
on Feb 4, 2026 - added a commit that references this issue
on Feb 5, 2026 - added a commit that references this issue
on Feb 23, 2026 - added a commit that references this issue
on Feb 24, 2026 - added 2 commits that reference this issue
on Feb 25, 2026
As a way to support the more unique use-cases that developers can come up with that our library doesn't support out of the box (see below for example bugs), and continue to support backward compatibility to our existing users, we'd like to return the raw response object from the API to all API calls. This will additionally provide an less intrusive way for developers to migrate their code from the generic libraries to our more idiomatic library.
Proposal for documented object name in docs:
rawBody,rawResponse,response,resp,apiResponse?Addresses #427
Addresses #342