cache stripe_customer

[gregnewman]

What's this PR do?

So the api doesn’t get called everytime Customer.stripe_customer is called, use a cached property.

Where should the reviewer start?

How should this be manually tested?

Any background context you want to provide?

What ticket or issue # does this fix?

Issues: #340

Definition of Done (check if considered and/or addressed):

• [] Does this contain breaking changes? No
• [] Does this add new dependencies? No
• [] Will this feature require a new piece of infrastructure be implemented? No
• [] Did you update internal documentation appropriately? Yes

[blueyed]

Is it necessary to invalidate the cache in some case(s)?

[paltman]

I think we are fine: 1. Most use cases will only populate this for the lifetime of the web request/response. 2. The Stripe id doesn't change for an object.

…

Sent from my iPhone

On Aug 26, 2017, at 1:48 PM, Daniel Hahler ***@***.***> wrote: @blueyed commented on this pull request. Is it necessary to invalidate the cache in some case(s)? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[blueyed]

Thank you!