Timeline for Proper design for a class with one method that can vary between customers
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 21, 2016 at 22:57 | comment | added | Andrew | That looks more promising. :) | |
| Dec 21, 2016 at 22:48 | history | edited | user188153 | CC BY-SA 3.0 | added 272 characters in body |
| Dec 21, 2016 at 22:44 | comment | added | user188153 | You could store the operations to be called for a customer in an array and use the customer ID to index it. | |
| Dec 21, 2016 at 22:23 | comment | added | Andrew | If I could create a comprehensive rule set I would. But each new customer might have their own set of rules. Also I would prefer the entire thing be contained in the code, if there is a design pattern to do this. My switch{} example does this quite nicely, but it's not very flexible. | |
| Dec 21, 2016 at 21:57 | history | undeleted | CommunityBot | ||
| Dec 21, 2016 at 21:54 | history | deleted | CommunityBot | via Vote | |
| Dec 21, 2016 at 21:53 | history | answered | user188153 | CC BY-SA 3.0 |