Add the 'customer.source.expiring' event and fix a typo #1210
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
|
r? @ob-stripe @karlr-stripe Thank you for the fix! Since we rename an event property it's likely a breaking change though. |
rattrayalex-stripe
changed the title
|
Hi, any updates on adding the |
|
@adamtay The event is in the library, it's just with a typo but you can use it. We're going to try to merge this one in the next few days |
ob-stripe
approved these changes
Jul 11, 2018
|
Released in 17.0.0. |
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.
Two changes here :
CustomerSourceExpiringStripeEvent for https://stripe.com/docs/api#event_types-customer.source.expiringCustomerSourcedDeleted->CustomerSourceDeletedI can back out the second change if we're worried about backwards compatibility or anything.