Timeline for Using the decorator pattern to populate entity properties
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 3, 2022 at 21:07 | comment | added | candied_orange | @filur you need to tell us WHY it's built up piece by piece. When it's built up. When that changes. If it's only ever added to or if it gets built differently... Sheesh just tell us why you want to do this. Just telling me you want to kill something doesn't tell me if need a sub machine gun, a nuke, or a fly swatter. | |
| Oct 3, 2022 at 20:49 | comment | added | filur | The product is built up piece by piece so I guess I'm after some kind of pipeline rather than building it all in once class that injects all the services needed to construct it. As time progresses more and more features are added to it, so it would be nice with an extensible approach. | |
| Oct 3, 2022 at 12:38 | comment | added | candied_orange | @filur still wondering what the motivation is. What do you need this flexibility for? | |
| Oct 3, 2022 at 8:00 | comment | added | filur | Yes, it feels like a misuse of the pattern. I was thinking a bit if a pipeline or chain of responsibility pattern makes more sense, but at the end of the day I guess it's just a matter of object composition? | |
| Oct 2, 2022 at 23:35 | history | answered | candied_orange | CC BY-SA 4.0 |