-
Notifications
You must be signed in to change notification settings - Fork 728
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 Charges API #1
Comments
Any ETA on Charges API or looking for help? |
Hi – Patches welcome! (In particular if they include tests and documentation update) I haven't looked for a few days, but from my notes I think the API should be something like
One of the things that made me pause implementing this was that I wasn't sure what the best way to return the error code / error description is when there are errors. An object instead of a string? If so then the other error handling should do that, too. |
Sounds great! Just committed changes to support Charge API. |
Fixed a couple little quirks. Was using a GET where it should be POST. |
Can you add some tests and then make a pull request? |
Yes. Will do soon. On Tuesday, October 4, 2011 at 5:32 PM, Ask Bjørn Hansen wrote:
|
Hi Chris, I changed the spaces to tabs and then squash merged it in so the history is clean. I "faked" the commit coming from you so you get credit in the history. :-) |
Thanks! I'll save you that step in future commits. On Wednesday, October 5, 2011 at 2:47 PM, Ask Bjørn Hansen wrote:
|
…d Customer data obj or via stripe.customers.{...}Card). See #1.
No description provided.
The text was updated successfully, but these errors were encountered: