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
We should be able to register implementations on a per tenant basis.
This will have to be in addition to the normal "lifetime" scopes.
So if I have an InstancePerExecutionContext() which controls the lifetime of instances of the implementation, InstancePerExecutonContext().PerTenant("9fd8188e-987f-4977-a813-fab79c719e9c") would decide that not only did we have a new instance of IFoo per execution context, it might be MyFoo for Tenant1 and YourFoo for Tenant2.
We'd obviously need a default implementation for other non-specified tenants.
Maybe something like InstancePerExecutionContext((ec) => //do some check with the execution context); might be a better more generic scope?
We should be able to register implementations on a per tenant basis.
This will have to be in addition to the normal "lifetime" scopes.
So if I have an InstancePerExecutionContext() which controls the lifetime of instances of the implementation, InstancePerExecutonContext().PerTenant("9fd8188e-987f-4977-a813-fab79c719e9c") would decide that not only did we have a new instance of IFoo per execution context, it might be MyFoo for Tenant1 and YourFoo for Tenant2.
We'd obviously need a default implementation for other non-specified tenants.
Maybe something like InstancePerExecutionContext((ec) => //do some check with the execution context); might be a better more generic scope?
┆Issue is synchronized with this Asana task
The text was updated successfully, but these errors were encountered: