Changed the answers for collections to return a new instance every time #536
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 fixes #510.
A change introduced in 1.10.2 added default answers for collections by using the helper
listOf()
,mapOf()
...functions.However, these all return the same instance of the corresponding collection, so when the
AnyValueGenerator
was used in creating matchers for recording calls the signature determination was broken: blocks stubbed asWhere both parameters are
List
s were being mistakenly matched asdoSomething(any(), eq([])
.By making sure that the `AnyValueGenerator´ always returns a new instance of collections, the signatures now take into account different values of the same type and result in proper matchers.