Justin Dalrymple

Fixed in https://github.com/jdalrymple/gitbeaker/pull/2258, the thrown error will include the response object as the 'cause' and use the description in the actual error object.

:rocket: Issue was released in [`37.0.0`](https://github.com/jdalrymple/gitbeaker/releases/tag/37.0.0) :rocket:

Exposing the response in the Error's cause property in #2258

Recently switched things to native fetch, is this functionality supported through the fetch api in any fashion?

Update: it will return blob, the user will need to determine how they want to handle the blobbed response, either converting to string via .toString(), or writing to a file,...

:rocket: Issue was released in [`37.0.0`](https://github.com/jdalrymple/gitbeaker/releases/tag/37.0.0) :rocket:

:rocket: Issue was released in [`37.0.0`](https://github.com/jdalrymple/gitbeaker/releases/tag/37.0.0) :rocket:

Yea, i was thinking of making another lib @gitbeaker/gql or something of the sort that would provide this support. Basically doing as you mentioned. There would be some changes since...

Trust me, the fact that its inconsistent APIs for both REST and GraphQL is the bane of my existence haha. Since the graphql implementation requires one to pass the query,...

Actually, upon looking at the code a bit more, you may be right. It could work just as an additional endpoint. Id have to tinker a bit i think.