-
Notifications
You must be signed in to change notification settings - Fork 4
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
feat: add iterable providers #22
Merged
ThirVondukr
merged 3 commits into
ThirVondukr:main
from
fadedDexofan:feat/iterable-providers
Jan 9, 2025
Merged
feat: add iterable providers #22
ThirVondukr
merged 3 commits into
ThirVondukr:main
from
fadedDexofan:feat/iterable-providers
Jan 9, 2025
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
990f5ab
to
b085919
Compare
5e5e1a8
to
910cdad
Compare
910cdad
to
934b2e8
Compare
cc @nrbnlulu class MiddlewareBase(abc.ABC, Generic[ReqT, ResT]):
@abc.abstractmethod
async def __call__(
self,
request: ReqT,
handle: Callable[[ReqT], Awaitable[ResT]],
) -> ResT:
pass
class FirstMiddleware(MiddlewareBase[ReqT, ResT]):
async def __call__(
self,
request: ReqT,
handle: Callable[[ReqT], Awaitable[ResT]],
) -> ResT:
return await handle(request)
class SecondMiddleware(MiddlewareBase[ReqT, ResT]):
async def __call__(
self,
request: ReqT,
handle: Callable[[ReqT], Awaitable[ResT]],
) -> ResT:
return await handle(request)
class ThirdMiddleware(MiddlewareBase[ReqT, ResT]):
async def __call__(
self,
request: ReqT,
handle: Callable[[ReqT], Awaitable[ResT]],
) -> ResT:
return await handle(request)
container = Container()
container.register(
Transient(FirstMiddleware, MiddlewareBase[str, str]),
Transient(SecondMiddleware, MiddlewareBase[int, int]),
Transient(ThirdMiddleware, MiddlewareBase[int, int]),
)
async with container.context() as ctx:
instances = await ctx.resolve_iterable(MiddlewareBase[int, int]) # type: ignore[type-abstract]
assert len(instances) == 2 # noqa: PLR2004
assert isinstance(instances[0], SecondMiddleware)
assert isinstance(instances[1], ThirdMiddleware) |
does it means you can register the same provider twice? |
Yes, but only with different implementations. Also there is validator for different provider lifetimes for same type. Just like in .NET DI |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added support for
Iterable
providers. This makes it possible to register multiple implementations for a single type and query them all at once.Behaves like .NET DI equivalent
https://learn.microsoft.com/en-us/dotnet/core/extensions/dependency-injection#service-registration-methods