Matcher instantiation depends of actual object type
Fix:
Adjusted API to work with arrays embedded in objects
The assumption is that whenever we get to the contains(T... items) with an array, the only possible way to get there with an array is by passing Object type reference (because of contains overloaded methods). Therefore we can safely add extra-check for embedded array
Fixes #301.
Caused:
actual
object typeFix:
The assumption is that whenever we get to the
contains(T... items)
with an array, the only possible way to get there with an array is by passingObject
type reference (because ofcontains
overloaded methods). Therefore we can safely add extra-check for embedded array