Difference between revisions of "Part pkg Mixin Refactor"
From Freeside
VitrcNavar (talk | contribs) |
m (Reverted edits by VitrcNavar (Talk); changed back to last version by Supaplex) |
||
| Line 1: | Line 1: | ||
| − | |||
=Description= | =Description= | ||
I'm looking at refactoring parts of the part_pkg architecture. The previous refactor was great, in that it made it easy to create new plan types, based on perl modules. The current problem that I see is there is only a linear inheritance. What I propose is to move to a Mixin style architecture, as many of the other parts of Freeside have done. This would allow us to create basic code for concepts such as 'Introrate' or 'Referrals' which could quickly be added to any package type, not copied and pasted into new sets. | I'm looking at refactoring parts of the part_pkg architecture. The previous refactor was great, in that it made it easy to create new plan types, based on perl modules. The current problem that I see is there is only a linear inheritance. What I propose is to move to a Mixin style architecture, as many of the other parts of Freeside have done. This would allow us to create basic code for concepts such as 'Introrate' or 'Referrals' which could quickly be added to any package type, not copied and pasted into new sets. | ||
''I agree we need more flexibility with price plans and the ability to "mix-and-match" pieces, doing something with Mixins sounds useful.'' --[[User:Ivan|Ivan]] 15:01, 22 October 2007 (PDT) | ''I agree we need more flexibility with price plans and the ability to "mix-and-match" pieces, doing something with Mixins sounds useful.'' --[[User:Ivan|Ivan]] 15:01, 22 October 2007 (PDT) | ||
Revision as of 10:56, 29 April 2009
Description
I'm looking at refactoring parts of the part_pkg architecture. The previous refactor was great, in that it made it easy to create new plan types, based on perl modules. The current problem that I see is there is only a linear inheritance. What I propose is to move to a Mixin style architecture, as many of the other parts of Freeside have done. This would allow us to create basic code for concepts such as 'Introrate' or 'Referrals' which could quickly be added to any package type, not copied and pasted into new sets.
I agree we need more flexibility with price plans and the ability to "mix-and-match" pieces, doing something with Mixins sounds useful. --Ivan 15:01, 22 October 2007 (PDT)
