-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add support for voiding invoices #444
Conversation
4 similar comments
👍👏👍 |
@@ -33,8 +33,7 @@ defmodule Stripe.SourceTest do | |||
|
|||
describe "detach/2" do | |||
test "detaches a source from a customer" do | |||
assert {:ok, %{deleted: true, id: "src_123"}} = | |||
Stripe.Source.detach("src_123", %{customer: "cus_123"}) | |||
assert {:ok, %{id: "src_123"}} = Stripe.Source.detach("src_123", %{customer: "cus_123"}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as of stripe-mock v0.39.0, this endpoint now returns a Stripe.Account object without a deleted
attribute to match against.
i raised a ticket on stripe-mock, since based on Stripe API docs, it seems like this should respond with a Stripe.Source object instead... but regardless, the response will no longer contain a deleted
attribute either way.
@snewcomer given that these changes are related to updating the stripe-mock version, not voiding an invoice, it seems cleaner to pull the version updates and this test change into a separate PR. let me know what you prefer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great @ktravers! Just one comment but otherwise g2g!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great @ktravers! Merging now 👍
closes #429
HOLD pending #439
Stripe.Invoice#void/2
function