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
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 to ListAutoPagingAsync(), there is no RequestId stored with object. The Charge.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 the ListAutoPagingAsync() call (and the other StripeResponse objects).
Describe alternatives you've considered
I can manaully write paginated calls to ListAsync() and using the StartingAfter or EndingBefore 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:
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 StripeResponse only on the top-level entity that is deserialized, but when you auto-paginate, the StripeResponse is put onto a page object that isn't accessible by the caller. We reach into the page object and return only the items in the page.
It would be easy to add a reference to StripeResponse on the list items when auto-paginating, but this feels wrong/inconsistent to me if we don't also follow through and add a similar reference to other non-top-level entities in other situations, and if we did that in this library we would probably want to add it for our libraries in other programming languages too. It's a real "if you give a mouse a cookie" situation.
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!
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: