Abstract our request handler resolution #33
Draft
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
Currently the default is to inspect all the assemblies in the current appdomain for types implementing `IRequestHandler` but it would be nice to be able to customize this resolution. This abstracts the concept out so you can provide your own resolver and suggest the types explicitly that should be used.
|
Maybe instead of the additional layer, just having a |
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.
Currently the default is to inspect all the assemblies in the current appdomain for types implementing
IRequestHandlerbut it would be nice to be able to customize this resolution. This abstracts the concept out so you can provide your own resolver and suggest the types explicitly that should be used.