Skip to content
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

'Disputed' attribute on charge is deprecated in favor of 'dispute' #13

Open
spakanati opened this issue Dec 3, 2012 · 5 comments
Open

Comments

@spakanati
Copy link

Charge objects in the Stripe API now have a dispute object instead of the disputed boolean:

https://groups.google.com/a/lists.stripe.com/forum/#!topic/api-discuss/dR3MCRKOtsc

The bindings need to be updated accordingly.

@mmatvien
Copy link

mmatvien commented Jan 4, 2013

Any traction on the fix for this ?

@rcino
Copy link

rcino commented Feb 18, 2013

Seeing the same issue

@markusjura
Copy link

me too

@markusjura
Copy link

Fixed the issue and changed the version to 1.1.3 in my fork: [email protected]:markusjura/stripe-scala.git

Repo available on: http://markusjura.github.com/stripe-scala

@d6y
Copy link

d6y commented May 20, 2013

I think Option[String] = None is a better choice for the field.

The spec is: Charge object now has a dispute attribute, which is a dispute object hash (https://stripe.com/docs/api#dispute_object) if the charge has been disputed and null if it hasn't.

d6y added a commit to d6y/stripe-scala that referenced this issue May 20, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants