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
While debugging, I have had the need to see the headers and other data used for the Stripe API request. It would be nice to either always include this data, or add a flag to the stripe.call() method to allow some raw request data to be sent back to the caller. What I did is modified the .call() method as follows:
However, in the case of an exception, I wouldn't see this because the .call() method doesn't catch exceptions and if one occurs, there would be no response struct being returned. Personally, I think it would be better for the .call() method to catch exceptions and therefore would always return a struct that would include the error information if an exception was thrown. That being said, I understand that could break existing applications so I'm not making that request.
The text was updated successfully, but these errors were encountered:
While debugging, I have had the need to see the headers and other data used for the Stripe API request. It would be nice to either always include this data, or add a flag to the
stripe.call()
method to allow some raw request data to be sent back to the caller. What I did is modified the.call()
method as follows:However, in the case of an exception, I wouldn't see this because the .call() method doesn't catch exceptions and if one occurs, there would be no response struct being returned. Personally, I think it would be better for the
.call()
method to catch exceptions and therefore would always return a struct that would include the error information if an exception was thrown. That being said, I understand that could break existing applications so I'm not making that request.The text was updated successfully, but these errors were encountered: