Conversation
Introduces providers.Alias, a thin delegating provider that registers one type (bound_type) and resolves it through whatever provider already handles another type (source_type). Lets a Group expose both the concrete implementation and an abstract base or Protocol without registering the implementation twice or losing the concrete binding via bound_type. resolve() looks the source provider up in providers_registry and forwards to container.resolve_provider(source), so overrides on either provider apply correctly and the source's cache (if any) is shared. get_dependencies() returns the source so cycles passing through an alias are caught by container.validate(). A missing source_type raises a new AliasSourceNotRegisteredError (ResolutionError subclass) eagerly during validation and at resolution time. The first version is pure delegation with no independent caching; if a separately-cached alias is ever needed, a cache_settings parameter can be added later. Closes #173 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
lesnik512
deleted the
173-add-alias-provider-for-interface-to-implementation-binding
branch
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Introduces providers.Alias, a thin delegating provider that registers one type (bound_type) and resolves it through whatever provider already handles another type (source_type). Lets a Group expose both the concrete implementation and an abstract base or Protocol without registering the implementation twice or losing the concrete binding via bound_type.
resolve() looks the source provider up in providers_registry and forwards to container.resolve_provider(source), so overrides on either provider apply correctly and the source's cache (if any) is shared. get_dependencies() returns the source so cycles passing through an alias are caught by container.validate(). A missing source_type raises a new AliasSourceNotRegisteredError (ResolutionError subclass) eagerly during validation and at resolution time.
The first version is pure delegation with no independent caching; if a separately-cached alias is ever needed, a cache_settings parameter can be added later.
Closes #173