add support for v2 deleted objects#1543
Merged
Merged
Conversation
Contributor
|
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? |
Contributor
Author
the manual changes won't. Plus I don't think we're running codegen against |
helenye-stripe
approved these changes
Aug 8, 2025
xavdid-stripe
added a commit
that referenced
this pull request
Sep 5, 2025
* add support for v2 deleted objects
helenye-stripe
pushed a commit
that referenced
this pull request
Sep 22, 2025
* 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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 thedeletedproperty 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
idandobject. To better represent this, we're now generating aV2.DeletedObjectclass 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_objectSee Also
DEVSDK-2588