Unexpected behaviour when console.log-ing or using lodash/fp/find about immutableassign HOT 3 CLOSED

I am fixing one of the unnecessary calls to the getProp(), however, for performance reason of following functionalities (which may not apply to you), I need call getProp() 2 twice:

1. ignoreIfNoChange option
2. when Proxy is not available (in the old browsers or mobile browsers)

That is why this library requires the getProp() to be a pure function (mentioned in README.md). I am more interested in your use case for lodash/fp/find, see if I can help to fix the issue.

Hint: getProp() should simple that only returns a property to be processed, you can you external context (also refer to example 7) to do additional processing outside the getProp() such as lodash/fp/find. E.g.,

const iassign = require("immutable-assign")
const findIndex = require("lodash/fp/findIndex")

const nested1 = { a:{ b:{ c:[ {id: 3}, {id: 4}, {id: 5}], d: 1 } } };
const nested2 = iassign(
    nested1,
    function (n, {index}) { return n.a.b.c[index]; },
    function () { return { id: 12}; },
    { 
      index: findIndex(s => s.id == 4, nested1.a.b.c) 
    }
);

from immutableassign.

@siassaj May I close the issue? Feel free to reopen the issue, if the above comments did not solve your problem.

from immutableassign.

@engineforce Thanks for responding, I was caught up with client work. I'll investigate it & take a look.

from immutableassign.