Unexpected behavior using .populate()

[mccormicka]

Unexpected behavior using .populate()

[mccormicka]

Hi @janek-bieser,
I have never tried to use populate with mockgoose.
I will look into this.
Thanks

[yads]

We're having the same issue.

[yads]

I may have tracked down the issue. When items are fetched in Mockgoose it uses _.clone to clone the item. However, nested objects don't get cloned and get assigned by reference. So when the populate goes in and updates the populated values, it's doing it on the references not the cloned values.

There needs to be some sort of recursive cloning since there is some custom logic re ObjectIds.

Edit: I think I have a fix for this issue, i'll test it some more and try to get it up tonight.

[mypark]

HI - any updates on the open pull request? I wanted to get the populate() function working on my unit tests and would be great if this solved the populate issue.

[mypark]

@yads so it looks like your fix works if you don't pass any select fields to the populate, but if you do it runs into the same issue .. e.g. .populate('createdBy', {fname:1, lname:1});

[ovaris]

It would be really really cool to have this fixed!

[winfinit]

pull request was merged and new 2.0.2 version in now on npm, thank you for your change.