Skip to content

feat: Containers feature #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from
Closed

feat: Containers feature #8

wants to merge 3 commits into from

Conversation

adrien-coye
Copy link
Contributor

@adrien-coye adrien-coye commented Aug 13, 2024

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

  • Remove the shared container.
  • Allow to use any container for registration / resolution.
  • New container management.
  • Allow for container retain policy (singleton, new …).
  • Proper test coverage of new code.

feat: Removed statically stored default container, now tracked by DependencyInjectionService
refactor: Removed the notion of Service from the code, as a container can have many retain strategies
@adrien-coye adrien-coye changed the title feat: Containers feat: Containers feature Aug 13, 2024
Copy link

@adrien-coye
Copy link
Contributor Author

Not happening soon. Discarding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant