Skip to content
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

Allow a service to be marked as not aliasable #286

Open
cspray opened this issue Mar 13, 2023 · 0 comments
Open

Allow a service to be marked as not aliasable #286

cspray opened this issue Mar 13, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@cspray
Copy link
Owner

cspray commented Mar 13, 2023

It is possible that an abstract service managed by Annotated Container should not be implicitly aliased to a single concrete service. For example, labrador-kennel/async-event Listener should not be implicitly aliased. Need to think about how to mark this on the service and what other implications this might have, particularly around alias resolution.

@cspray cspray added the enhancement New feature or request label Mar 13, 2023
@cspray cspray self-assigned this Mar 13, 2023
@cspray cspray added this to the v2.x Release milestone Mar 13, 2023
@cspray cspray moved this to Todo in Annotated Container Mar 13, 2023
@cspray cspray removed this from the v2.x Release milestone May 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Todo
Development

No branches or pull requests

1 participant