Add a core feature that allows to resolve all dependencies in a certain Scope.
This can be done in user space resolving all Resources and compiling the "per scope" map as well as binding some means of access to it. Another approach could be to allow resolving a sub Injector context that only contains that scope. This most likely requires some form of injector implementation support.
In this context it also seems useful if one could annotate instance, like a scope, with some markers and resolve instances by the markers. Again the resolution could be build in user space based on Resources. Its unclear where or in what form the annotations would be stored and how the are declared. Logical would be a system similar to the plug-in mechanism where these are just binds of a special type that somehow link to another resource.
Add a core feature that allows to resolve all dependencies in a certain
Scope.This can be done in user space resolving all
Resources and compiling the "per scope" map as well as binding some means of access to it. Another approach could be to allow resolving a subInjectorcontext that only contains that scope. This most likely requires some form of injector implementation support.In this context it also seems useful if one could annotate instance, like a scope, with some markers and resolve instances by the markers. Again the resolution could be build in user space based on
Resources. Its unclear where or in what form the annotations would be stored and how the are declared. Logical would be a system similar to the plug-in mechanism where these are just binds of a special type that somehow link to another resource.