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.
Hello! I've tried bumping the spec3.json file to the most recent one provided by Stripe.
Following your codegen instructions, there were surprisingly few issues. I did run into a few things however, especially in some apparently new fields that the Stripe API lists as type
hash
. I've marked these areas with TODO's in the PR. There are about a dozen of them.I'm posting the PR early, as a draft, in case it's obvious to the maintainers how I should fix this. If you already have your own process for bumping the spec, please feel free to ignore me :) If not, and a bump would be useful, I'd love to help polish this up.
For us, the need for a bump the spec was driven by our use of Stripe subscriptions. The
CreateSubscriptionItems
schema has changed to accept aPrice
rather than aPlan
, and that's the API we would like to program against.