contain/include bug introduced in v1.9

[adambiggs]

After upgrading from v1.8.1 to v1.9, I noticed a failed assertion when testing that an array contains an object instance.

Example:

var obj = { foo: 'bar' };
var arr = [ obj ];

arr.should.contain(obj);
// AssertionError: expected [ { foo: 'bar' }, unique: [Function] ] to have a property 'foo'

Seems like a breaking change with contain/include assertions, but I couldn't find any mention of it in the changelog.

[vesln]

Confirmed. On top of my head I can tell that #230 was touching include/contain, but not sure it's causing the issue. Regardless the root cause, it should be fixed and a new version will be released. Thanks for letting us know! I'll keep you posted

[kirill-konshin]

The solution can be (file assertions.js):

// change from
if (_.type(val) === 'object') {
// to
if (_.type(val) === 'object' && _.type(obj) !== 'array') {

[lo1tuma]

I have the same problem.
Does #244 fix this issue? If so, can you release a patched version on npm?

[logicalparadox]

Released in 1.9.1. View release notes.