feat: Containers feature #8
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Abstract
The notion of Containers brings some nice flexibility to the library.
It will allow us to fix some issues with complex project setups, and more finely manage DI in quickly growing apps.
Breaking change
There is no longer a default, statically defined shared container.
We expect now expect the user of the library to explicitly init an track an
DependencyInjectionService
to manage Containers.Apps (still on the fence about this) will now be required to explicit containers to
Inject
property wrappers (or subclass them an pass the correct container).todo