New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to get StripeResponse.RequestId from ListAutoPagingAsync() calls #2771
Comments
Hi @antfitz, thank you for the feature request! I agree it could be useful to see the request ids corresponding to the pagination request and it's unfortunate you can't do this when autopaginating. Part of the issue is, normally we populate It would be easy to add a reference to I will discuss with the team, but I don't think we'll be able to provide a solution immediately. If you need the RequestId, I recommend manually paginating for now. Thank you for the request! |
Thanks - will leave it with you guys! |
Hi there @antfitz ! We're going to keep this issue open to track it, if that's OK. To help us think about how useful adding this would be, can you share how you are using this request ID? |
Is your feature request related to a problem? Please describe.
Currently we sync data from the Stripe API and utilise the AutoPaging functionality of the SDK. When we receive the
Stripe.Charge
object back from looping a call toListAutoPagingAsync()
, there is no RequestId stored with object. TheCharge.StripeResponse
object is null.Describe the solution you'd like
It would be good to be able to store the
RequestId
against each object returned from theListAutoPagingAsync()
call (and the otherStripeResponse
objects).Describe alternatives you've considered
I can manaully write paginated calls to
ListAsync()
and using theStartingAfter
orEndingBefore
and get the headers for each call, but its just much easier to use the provided auto paging functionality of the SDK.Additional context
No response
The text was updated successfully, but these errors were encountered: