fix: mock setup for generic types (#141) #141
Merged
Conversation
This file contains hidden or 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
Signed-off-by: Tronje Krop <tronje.krop@jactors.de>
Signed-off-by: Tronje Krop <tronje.krop@jactors.de>
Signed-off-by: Tronje Krop <tronje.krop@jactors.de>
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.
This pull request fixes the mock setup support for generic types. The mock storage now correctly distinguishes between different generic mock types allowing the define requirements correctly for these. Before, the mock setup created a new mock on each generic setup requests - only specific setup where correctly mapped. Now the mapping is done correctly by the
reflect.Typeinstead of thereflect.Value.