Purchases: Move purchases logic in the API #2783
Labels
[Feature] Purchase Management
Related to managing purchases such as subscriptions, plans, history, auto-renew, cancellation, etc.
[Status] Stale
[Type] Enhancement
Milestone
As discussed in #2602 (comment), we shouldn't have that much logic in our purchases functions. To be more specific the logic that determines whether a purchase is cancelable or is removable should live in the API. As such, we should take advantage of the
is_cancelable
property returned by the endpoint which we don't use at all in Calypso.We should also take this opportunity to remove any unnecessary property from the purchases assembler such as
subscribedDate
ortagLine
- there is no need to keep them around.The text was updated successfully, but these errors were encountered: