Fixed incorrect method name from v1 to v1.1 changeover

[icook]

This was figured out from experimentation with the v1.1 library, so I'm not sure if it's 100% correct.

[mjallday]

Great catch.

i think this is why we need a generation tool rather than copying the rev0 code.

@icook shoot us an email to support@balancedpayments.com if you'd like some swag to say thanks :)

[mahmoudimus]

@icook you sure you want to try rev 1.1 ;) ? if you are, I'll assign @remear to help see how you use it to work through any warts. Also happy to feature you on our upcoming blog release. We're relatively close to releasing it publicly.

[mahmoudimus]

@mjallday why is this get - can we change this to retrieve?

[mjallday]

@mahmoudimus it's the wac library, not the python client.

[mahmoudimus]

that should be fixed before we release -- at least alias it to retrieve for now.

[icook]

Actually sent an email earlier today about using v1.1. We're probably at least a month away from release, but we could definitely put a coming soon page up or something...

We're looking at v1.1 because we are handling Card/Bank Accounts abstraction from users on our end and I'd like to make debits independent of Customer objects.

[mjallday]

@icook after discussions we're going to go the fetch route to help differentiate between the HTTP verb GET and the actual fetching of the resource. .get will continue to work but going forward the documentation for 1.1 clients will refer to a fetch method.

we've updated the docs and client library to reflect this.

thanks for bringing this up and please continue to provide feedback on 1.1, it's really valuable to us :).

[icook]

Thanks for the notice, I'll change my stuff accordingly. I'll definitely let you know if I find any other quirks.