Merge upstream changes #1
Open
Conversation
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
* Does not link refunds through charges like I would expect because creation of payment intents do not seem to create and/or link charges
`Stripe::Charge.create` and `Stripe::Refund.create` will throw `NoMethodError: undefined method `receipt_url'`. Add `receipt_url` to charge and refund mock data to fix this error
Add :off_session, :trial_from_plan, and :expand params to allowed params in subscription
Fix ruby 2.7 deprecation warnings
Support Stripe Connect by adding stripe_account header namespace for customers
Create price
This only throws an error if both customer and subscription aren't present, which is more consistent with the real API.
…sage Fixes erroneous error message when
Properly set the status of a trialing subscription
Add allowed params to subscriptions
Remove unnecessary check on customer's currency
Add update_payout
fix calls to use raise instead of throw
Add simple support for us bank accounts
…est for payout.update method
"Remove support for charges on PaymentIntent" - https://docs.stripe.com/changelog#16-november-2022
Better tests for payout
Removed charges on PI and added latest_charge
* Allow stripe < 8 * Add `application_fee_percent` # Conflicts: # lib/stripe_mock/data.rb * Add :cancel_at, :end_at * Add :price to :subscription_items * Add :pause_collection to Subscription * Add :has_more to subscription_items list * Remove :mock_price from Subscription * Customer from subscription on upcoming_invoice * Get plan amount from Plan or Price * Allow stripe 12 --------- Co-authored-by: Alexander Mamonchik <[email protected]>
Add has_more to Subscription.items data
When booting the stripe-mock-server it can be useful to have Ruby `require` in additional files if you need to patch `StripeMock` in some way. This is mostly useful for differences when you're running on an older version of the Stripe API and need to tweak `StripeMock`'s behavior until your Stripe API version is upgraded to be compatible. When using `StripeMock` directly within a Rails app, for example, this is unneeded as you can do the same thing via a Rails initializer file. But if running the `StripeMock` server standalone - for use with front end tests, for example, you might pass this new flag like this: --require config/initializers/stripe_ruby_mock
Add `require` option to require additional file
…equirements Account: replace deprecated `verification` hash by `requirements`
Add tax ID endpoints and data
* add missing mock production attributes * try to fix github action * try to fix github action * fix mock product test * fix github action * try to use setup-ruby@v1
Actions uses only supported ruby versions
to Ruby 3.4.0 Co-authored-by: lucas-cp-pessoa <[email protected]>
* Add support for Stripe version 13 * Support all v13 stripe versions * Add compatibility with new version of Stripe * Trigger Build * Add support for Stripe version 13 - Add Compat module for checking Stripe gem version - Add Appraisals gem for testing - Update Client and Instance code to handle both version 12 and 13 of Stripe - Update specs * Add object key to discount * Refactor compatibility module Make method name more intuitive * Add client_instance method * Update GitHub action to run specs against multiple stripe versions (cherry picked from commit 41cf163) * Update gemfile lock Run bundle exec appraisal update (cherry picked from commit 6063282) * Add dependency update instructions to README (cherry picked from commit a83642d)
* Disabled cack for first run after merge #931 * force execute bundle install
## What Makes it possible to set cancellation_details when marking a subscription for cancellation https://docs.stripe.com/api/subscriptions/update#update_subscription-cancellation_details
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
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.
No description provided.