You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My app has the following exception type which is used to bail out from HTTP requests which returned something unexpected. There are many APIs in the wild that return a 200 ok with a weird custom data structure in the response that indicates an error. The following type covers all such situations because it allows the raw response AND the raw request to be logged for debugging.
HOWEVER, as a user of the wreq library the only way to get hold of the original Request is via the prepareGet and preparePost methods, which are inside hidden/internal modules.
Any thoughts on exposing these Internal modules (with a big fat warning, if required)?
The text was updated successfully, but these errors were encountered:
My app has the following exception type which is used to bail out from HTTP requests which returned something unexpected. There are many APIs in the wild that return a
200 ok
with a weird custom data structure in the response that indicates an error. The following type covers all such situations because it allows the raw response AND the raw request to be logged for debugging.HOWEVER, as a user of the
wreq
library the only way to get hold of the originalRequest
is via theprepareGet
andpreparePost
methods, which are inside hidden/internal modules.Any thoughts on exposing these
Internal
modules (with a big fat warning, if required)?The text was updated successfully, but these errors were encountered: