Add constants for payment intent cancellation reasons #1526
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
|
|
|
Thanks for the contribution! I've fixed the underlying problem in our library generator, so this enum will be added once e2b090c#diff-5239e074340aff1a427e536f1944bba3ff00d356fafb24a988da1505c7236da7 is merged for our next release. I'll merge your PR, even though it will get wiped by the generated version, so you get committer credit! |
richardm-stripe
approved these changes
Jul 19, 2023
|
Thank you @richardm-stripe for the effort! Which stack are you using for the library generator? I guess based on OpenAPI descriptions. I'm curious about it; it would be worth to explore for some APIs I am currently developing! |
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.
Add the different values available for cancellation reason field when a payment intent is cancelled.
Values retrieved from API documentation:
Similar approach as it was already done for statuses: