Timeline for Limits of dependency injection
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 23, 2017 at 11:28 | comment | added | Walfrat | Dependency injection is merely passing parameters into constructors or setter. If it gets harder to manage that, it's likely that your design have a problem. Note that some container can also manage the lifecycle of your object, which means you can have some of your dependencies that instead of being singleton, they're session-scoped, or request-scoped (which is basically the same than thread scope in the context of handling an HTTP request). | |
| Oct 21, 2017 at 4:10 | history | edited | maaartinus | CC BY-SA 3.0 | added 306 characters in body |
| Oct 21, 2017 at 3:50 | history | edited | maaartinus | CC BY-SA 3.0 | added 777 characters in body |
| S Oct 20, 2017 at 10:38 | history | suggested | Emerson Cardoso | Added new tag for OO | |
| Oct 20, 2017 at 10:19 | review | Suggested edits | |||
| S Oct 20, 2017 at 10:38 | |||||
| Oct 20, 2017 at 10:01 | comment | added | Sean Burton | Yeah it seems like this is the sort of concern that the response shouldn't need to know about at all. | |
| Oct 20, 2017 at 9:58 | answer | added | Emerson Cardoso | timeline score: 5 | |
| Oct 20, 2017 at 8:23 | comment | added | Zymus | Have you considered an MyResponseSerializertype, then have one that returns Json, one with stack trace details, etc. | |
| Oct 20, 2017 at 6:33 | history | asked | maaartinus | CC BY-SA 3.0 |