You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dotkernel API needs to create handlers using its own factory and inject dependencies (using setters) instead of getting them through the constructor.
This way handler constructors will not to be pulluted by the same key dependencies in each class.
Instead, hey can inject only those dependencies that they require for the tasks they need to perform.
Additionally, handlers have other dependencies (services, configs etc) that should be injectable through the constructor, as before.
For this, dot-dependency-injection should expose a solution that allows factories to read the dependencies as an array of ready-to-use instances.
The text was updated successfully, but these errors were encountered:
I just found out that I can solve my issue in Dotkerne API without having this feature.
Adding this feature to dot-dependency-injection is now optional - if we see value in it, we can keep it. Else, it can be discarded.
Dotkernel API needs to create handlers using its own factory and inject dependencies (using setters) instead of getting them through the constructor.
This way handler constructors will not to be pulluted by the same key dependencies in each class.
Instead, hey can inject only those dependencies that they require for the tasks they need to perform.
Additionally, handlers have other dependencies (services, configs etc) that should be injectable through the constructor, as before.
For this, dot-dependency-injection should expose a solution that allows factories to read the dependencies as an array of ready-to-use instances.
The text was updated successfully, but these errors were encountered: