Timeline for Patterns for passing context through a method chain
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 28, 2015 at 16:12 | review | Suggested edits | |||
| Nov 28, 2015 at 16:28 | |||||
| Nov 28, 2015 at 16:08 | comment | added | Jamie McCrindle | @JonathanvandeVeen I agree, dependency injection is a valid solution. In fact it's the one I'd most often pick. | |
| Nov 28, 2015 at 4:21 | comment | added | Kevin Krumwiede | @DavidArno Dependency injection frameworks don't get rid of these kinds of dependencies, they just move them. The magic is that they move them outside your classes, to a place where testing is Somebody Else's Problem. | |
| Nov 27, 2015 at 16:47 | comment | added | David Arno |
@JonathanvandeVeen, surely the very act of passing dependency around via parameters is dependency injection?
|
|
| Nov 27, 2015 at 14:35 | comment | added | Jonathan van de Veen | I almost agree completely. Dependency Injection may be another Non-"hacky"aproach. | |
| Nov 27, 2015 at 13:10 | history | answered | David Arno | CC BY-SA 3.0 |