Timeline for How do I structure my code to avoid tight coupling between my parent and child classes?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 8, 2018 at 16:52 | history | edited | pieperu | CC BY-SA 3.0 |
added 310 characters in body
|
| Oct 28, 2016 at 1:23 | comment | added | George | I love extension methods for adding functionality to a class that logically makes sense directly on that class, but the problem in this case is that ChildClass must override MethodA (B, C, D...) from its parent DataProvider. MethodA must call to SomeObject that only ChildClass knows how to instantiate. I could write an extension method MethodA, but that method isn't going to be able to reference an object field on ChildClass. | |
| Oct 27, 2016 at 21:59 | history | edited | pieperu | CC BY-SA 3.0 |
added 315 characters in body
|
| Oct 27, 2016 at 17:03 | history | edited | pieperu | CC BY-SA 3.0 |
added 459 characters in body; added 35 characters in body; deleted 57 characters in body
|
| Oct 27, 2016 at 16:54 | history | edited | pieperu | CC BY-SA 3.0 |
added 12 characters in body
|
| Oct 27, 2016 at 7:58 | history | answered | pieperu | CC BY-SA 3.0 |