Add support for service key registration #262
Merged
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.
Overview
This PR adds support for keyed service registration in the
Scanmethod, enabling compatibility with .NET 8's keyed dependency injection feature. This allows users to specify service keys during scanning, aligning with theAddKeyedSingleton/AddKeyedScoped/AddKeyedTransientpattern introduced in .NET 8.Problem
Previously, there was no way to register services with keys when using Scrutor's scanning capabilities. Users who wanted to leverage .NET 8's keyed DI feature had to manually register services, losing the benefits of convention-based scanning.
Solution
Added two new methods to
ILifetimeSelector:WithServiceKey(object serviceKey)- Registers all scanned services with a fixed service keyWithServiceKey(Func<Type, object?> selector)- Registers services with dynamic keys based on a selector functionUsage Examples
Fixed Service Key
Register all scanned services with the same key:
Dynamic Service Key
Use a selector function to assign different keys based on the implementation type: