-
Notifications
You must be signed in to change notification settings - Fork 458
add support for v2 deleted objects #1543
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
Conversation
I'm peaceful with this but won't the generated changes get removed by CI since we'll go back to using the proto spec to generate the SDK? |
the manual changes won't. Plus I don't think we're running codegen against |
* add support for v2 deleted objects
* Update generated code for v1868 and 2025-07-30.basil (#1541) Co-authored-by: Stripe OpenAPI <105521251+stripe-openapi[bot]@users.noreply.github.com> * Bump version to 12.4.0 * Introduce V1 namespaces in StripeClient (#1549) * Introduced V1 namespaces * Updated migration guide link * Import available http libraries more efficiently (#1553) * replace import stragety, fix some tests [skip ci] * wip fixing tests [skip ci] * [claude] fix tests * formatting * test cleanup * tests are fast * final cleanup * remove comment * remove accidential files * tweak import logic * Update generated code for v1932 and 2025-08-27.basil (#1544) Co-authored-by: Stripe OpenAPI <105521251+stripe-openapi[bot]@users.noreply.github.com> Co-authored-by: Ramya Rao <100975018+ramya-stripe@users.noreply.github.com> * Add section on private preview SDKs in readme (#1554) * Bump version to 12.5.0 * Add private-preview branch to CI workflow triggers 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * fix: paginate backwards if `starting_after == None` (#1563) This fixes the case where `starting_after` is present in `_retrieve_params` but is `None` so that the `auto_paging_iter` correctly paginates backwards. closes #1562 * Bump version to 12.5.1 * add support for v2 deleted objects (#1543) * add support for v2 deleted objects * revert event destination return type *⚠️ Build SDK w/ V2 OpenAPI spec (#1565) * generate w/ v2 openapi spec * gen again * gen * Updated stripeclient snippets in Readme.md (#1528) * Don't use mutable default arguments (#1570) * generate default assignments * add mutable args linter and fix errors * type generated args more accurately * only initialize optional params when needed * generate private-preview --------- Co-authored-by: stripe-openapi[bot] <105521251+stripe-openapi[bot]@users.noreply.github.com> Co-authored-by: Ramya Rao <ramya@stripe.com> Co-authored-by: prathmesh-stripe <165320323+prathmesh-stripe@users.noreply.github.com> Co-authored-by: Ramya Rao <100975018+ramya-stripe@users.noreply.github.com> Co-authored-by: Michael Broshi <mbroshi@stripe.com> Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Ryan Causey <ryan.causey@munipal.io>
Why?
The typing of delete calls has always been a little confusing in V1: SDKs say they return an entire object (like a
Customer
) but with thedeleted
property set toTrue
. That's true for some APIs but not for others. For consistency, we just always say you get a "real" object.V2 APIs are more strict about the data they return: there's only ever
id
andobject
. To better represent this, we're now generating aV2.DeletedObject
class that is returned from all v2 delete calls. This PR includes that generated class, but APIRequestor-related code to use it when appropreate.What?
_convert_to_stripe_object
See Also
DEVSDK-2588