Undecorated service succeeds, but decorated service fails (#378) #379
+128
−0
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
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.
Demonstrates issue #378.
The container is set up to allow dependencies of a shorter lifespan
(it's a large legacy app that has a lot of code relying on this setup).
The default reuse is Scoped, instead of Transient.
Resolution occurs within the open scope.
Decorated service is set up to be created using a factory method.
Undecorated service resolves just fine.
Decorated service resolution throws an exception.
Both services are singletons, and both have the same non-singleton dependencies.