Implement the Customers resource about balanced-python HOT 8 CLOSED

• I disagree about .hold on a customer. You should perform a hold on a Card, not on a customer.
• Also if you have an add_card method, there should be a remove_card method. I think the proper name should be associate_card and deassociate_card.

from balanced-python.

hold should at least be a helper.

I posit that most customers will have a single valid card associated at any given time. Writing customer.hold is much easier for the person integrating Balanced than writing card = customer.cards.filter(is_valid=True)[0]; card.hold.

from balanced-python.

• We return a primary source uri don't we?

I would write a property that will return a most_recently_added_card and
a most_recently_added_bank_account

On Mon, May 6, 2013 at 2:51 PM, Marshall Jones [email protected]:

hold should at least be a helper.

I posit that most customers will have a single valid card associated at
any given time. Writing customer.hold is much easier for the person
integrating Balanced than writing card =
customer.cards.filter(is_valid=True)[0]; card.hold.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/35#issuecomment-17510631
.

from balanced-python.

default_card/default_bank_account? How does most_recently_added... work with setting cards/bank_accounts to invalid?

from balanced-python.

most_recently_added_bank_account should just be default_bank_account where the order of items returned is:

1. whatever was set to default
2. most recent, valid card

same for cards.

from balanced-python.

That is perfect for me. Can we call it "active_card" and "active_bank_account" then?

from balanced-python.

Implementing in #36

from balanced-python.

Done!

from balanced-python.