Timeline for What is the benefit to having pure POCO models?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 10:01 | history | edited | CommunityBot |
Commonmark migration
|
|
| Oct 14, 2018 at 12:04 | history | edited | candied_orange | CC BY-SA 4.0 |
added 5 characters in body; added 2 characters in body
|
| Jun 6, 2017 at 13:31 | comment | added | Oliver | I wonder how well Fowler's presentation would have gone if he had called them POO? | |
| Jun 5, 2017 at 14:03 | vote | accept | Jesse | ||
| Jun 5, 2017 at 11:29 | comment | added | KRyan | I have also seen “PODO” for “plain old data object” to avoid any sort of language specifier in the acronym. PODO sounds a little silly (kinda sounds like an epithet you’d hear on Tatooine, to me), more so than POJO or POCO I suppose, but significantly less silly than POO. | |
| S Jun 5, 2017 at 10:41 | history | suggested | Appulus | CC BY-SA 3.0 |
Fixed grammar
|
| Jun 5, 2017 at 10:36 | review | Suggested edits | |||
| S Jun 5, 2017 at 10:41 | |||||
| Jun 5, 2017 at 5:18 | comment | added | candied_orange | I can do a whole host of silly things for simplicity's sake. What I don't like is A knowing about B. A doesn't use B so there isn't a need to define a proper A owned interface to talk to B through. As far as I can tell A is a collection. So A should deal with B through a <T> so it doesn't have to know a thing about it. | |
| Jun 5, 2017 at 4:59 | comment | added | Jesse |
I had the direct dependency to B for simplicity's sake, Ideally these would both implement interfaces. But A still has a list of IInterfaceB. Is there something wrong with the AddChild method if the children are loosely coupled through interface references?
|
|
| Jun 5, 2017 at 4:44 | history | answered | candied_orange | CC BY-SA 3.0 |