You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am planning to create a new module for subscriptions: subscription_oca_purchase.
The module will inherit subscription_oca and do the same for purchases. A subscription_type field will be added to subscriptions and subscriotion templates to make the logic.
Also, a little refactor to the subscription_oca will be needed. I have considered the following changes:
Adding the subscription_type field with only the "sale" value.
Set required=False in the pricelist field of the subscriptions, and adapt to the change all the functions related to pricelists of the subscription and subscription lines models.
Is anyone interested?
Does anyone see any problems with refactoring oca_subscription?
Other thoughts on this?
The text was updated successfully, but these errors were encountered:
Hi, I am planning to create a new module for subscriptions: subscription_oca_purchase.
The module will inherit subscription_oca and do the same for purchases. A subscription_type field will be added to subscriptions and subscriotion templates to make the logic.
Also, a little refactor to the subscription_oca will be needed. I have considered the following changes:
Is anyone interested?
Does anyone see any problems with refactoring oca_subscription?
Other thoughts on this?
The text was updated successfully, but these errors were encountered: