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
It would be beneficial to have more precise control over passing dependency overrides, along with support for named bindings. Currently, our approach is as follows:
It would be beneficial to have more precise control over passing dependency overrides, along with support for named bindings. Currently, our approach is as follows:
container.Resolve<Service>([ instance1, instance2... ])
In this setup, type overrides are automatically resolved based on their type and the classes/interfaces they implement, as far as I know.
I propose introducing a wrapper that the resolver could use to extract specific additional information, like this:
container.Resolve<Service>([ Arg<IExactType1>(instance1), Arg<IExactType2>("name", instance2)... ])
This approach would enable us to specify dependencies more explicitly and manage named bindings more effectively.
The text was updated successfully, but these errors were encountered: