Timeline for Applying Composition Over Inheritance to Page objects
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 30, 2019 at 11:49 | vote | accept | Nathan Arthur | ||
| May 27, 2019 at 12:01 | comment | added | Robert Bräutigam |
The problems start with pulling data out of objects. As soon as you do that, now you are responsible for knowing what to do with it, hence the need to start sharing knowledge all over the place. Unfortunately you don't have enough details for me to draft some design. But, you should start with what you need these objects to do, and build from there. Do you need a Page produce a HTML page? A JSON object? Start with that, try to work your way backwards.
|
|
| May 27, 2019 at 11:33 | review | Suggested edits | |||
| May 27, 2019 at 14:45 | |||||
| May 26, 2019 at 18:26 | answer | added | casablanca | timeline score: 0 | |
| May 26, 2019 at 17:41 | answer | added | Greg Burghardt | timeline score: 0 | |
| May 26, 2019 at 15:31 | answer | added | Bohdan Stupak | timeline score: 2 | |
| May 26, 2019 at 15:25 | comment | added | Robert Harvey | Where you made the wrong turn is you decided to favor composition over inheritance without considering the tradeoffs. Inheritance is not a dirty word; it is a tool, and like any other tool, it has its appropriate uses. | |
| May 26, 2019 at 15:07 | history | asked | Nathan Arthur | CC BY-SA 4.0 |