Timeline for How to reuse parts of dependency injection composition root
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 13, 2017 at 19:42 | vote | accept | xlecoustillier | ||
| Oct 12, 2017 at 21:16 | answer | added | Stephen Byrne | timeline score: 2 | |
| Oct 12, 2017 at 20:27 | answer | added | Ewan | timeline score: 3 | |
| Oct 12, 2017 at 19:48 | comment | added | xlecoustillier | @RobertHarvey That's the point. It's a single application with a lot of entry points, meaning a lot of nuances between each composition root, but also a lot of duplication. I have solutions, I'm just wondering if someone has some other interesting approaches to that problem, as I'm not really satisfied with what I came up with until now. | |
| Oct 12, 2017 at 19:42 | comment | added | Robert Harvey | In any case, that article already describes in detail the relevant issues. I'm not sure what we can add to that discourse here, other than "the best practice is generally the one that most effectively meets your specific requirements." | |
| Oct 12, 2017 at 19:40 | comment | added | Robert Harvey | According to the article you linked, a composition root refers to a single application, and your question is about a single application. | |
| Oct 12, 2017 at 19:33 | history | asked | xlecoustillier | CC BY-SA 3.0 |