Navigating trough the
sale.subscription module, I found out that (as how the subscription module is written to this date) don’t use any feature of Sale. So i want to discuss cut out Sale from the dependency list (and change the menu items accordingly).
Motivation (non a strong one):
Consider a simple association; they need to generate a recurring invoice (for the obligatory membership fee) but not a full sale workflow (association are not in the sale business, usually).
circumstantial evidence/our user case:
I’m the accountant of a medium/small association, and in our case, we don’t use the sale workflow.
Possible counter arguments:
sale_subscription_assetuses the sale module and the subscription module, so it can be problematic (didn’t check the code)
- possible roadmap feature that make use of the sale workflow
What we gain
- almost nothing, but it will make me happy
- and modularity, don’t forget about that
- Just ignore the sale workflow