Updating charge.captured to use PI instead of Charge #959
Conversation
This file contains 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
|
I'm confused... I pulled latest right before pushing this? And I just checked again and it states Everything up-to-date. What am I missing? |
|
@bensnell-stripe I think you're fine? The test suite has a race condition we haven't been able to find yet but there don't appear to be any other issues other than needing a code review (I'm rerunning the failed one now) |
|
r? |
thanks! |
etsai-stripe
approved these changes
Sep 2, 2022
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.
Reviewers
r? @stripe/developer-products
cc @stripe/developer-products
Summary
Updating the charge.captured trigger to create a PaymentIntent instead of creating a Charge.
Tested locally and looks good:
