Timeline for Shopping cart business rules
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 15, 2017 at 23:18 | comment | added | radarbob |
re: a 'type' property vis-a-vis subclass. Granting @tcchb0t comment, I am and was ambivalent about the suggestion - I really don't know what's up with a Product at this point. But it is a way to curtail subclass explosion when there is much commonality.
|
|
| Jul 15, 2017 at 13:00 | comment | added | Francis Ade | Sorry about that. my focus and confusion was on how to code the rules.. I assume intricate details about a line item is not necessary. i was clearly wrong | |
| Jul 15, 2017 at 12:42 | comment | added | t3chb0t | @FrancisAde it has common attributes of a product. price, name, description oh, really? there is nothing about it in the question. | |
| Jul 15, 2017 at 12:36 | comment | added | Francis Ade | you made a lot of good points here. The membership being a product is because it is something that can be bought. it has common attributes of a product. price, name, description. | |
| Jul 15, 2017 at 7:11 | comment | added | t3chb0t |
You have my vote but this advice The Product can have a "type" is questionable. I think having subclasses for each product is much better since they can have different properties and you won't be able to cover them with a common class and if you do you'd have a bunch of unnecessasry ones for products that don't support them.
|
|
| Jul 15, 2017 at 4:47 | history | answered | radarbob | CC BY-SA 3.0 |