Simplify DI #329
Assignees
Labels
idea
A large scope idea that needs to be discussed before it can be implemented.
technical debt
Things that would make the code cleaner but deliver little to no value to users.
Milestone
Comments
ekolis
added
idea
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What needs to be cleaned up?
Dependency injection code is split across three classes right now:
DI in FrEee.Core.Utility: allows services to be registered and retrieved
DIRoot in FrEee.Core.Domain: allows services to be retrieved using properties for common services
Configuration in FrEee.Root: registers default service implementations
I think this could be cut down to two, though I'm not entirely sure how best to do that.
How will this benefit us?
Reduce complexity
What potential drawbacks are there to making this change?
Need to be careful to not break the whole concept of dependency injection by injecting too many assumptions
Related issues
#322 - original DI issue
The text was updated successfully, but these errors were encountered: