Add keyed service registration support #260
Open
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.
Summary
This PR adds support for registering services with a service key in Scrutor.
Currently, Scrutor does not provide a way to register keyed services.
With this change, developers can specify a key when registering a service via
ServiceDescriptorAttribute.Changes
ServiceDescriptorAttributeto allow an optionalServiceKeyproperty.ServiceKeyif provided.Motivation
Adding keyed services allows more flexible dependency injection scenarios,
such as having multiple implementations of the same interface and selecting them by key at resolution time.
Example