You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does this library support ES6 Map? For me the following example does not work correctly. 'm' is always empty in the setProp and therefore map3 (or mapX) contains always one element after adding further elements.
ES6 Map support is added in 1.0.36, please refer to example 9.
Note: even with the fix, getProp() won't be able to handle navigate into the map object, it only supports navigate upto the map object. E.g.,
// Works// Assume copyFunc option is setvarnested1={a: {b: newMap()}};nested1.a.b.set("c",{"d": 100})varnested2=iassign(nested1,(m,ctx)=>m.a.b,(b)=>{b.set(0,'first');returnb;});
// Will not work// Assume copyFunc option is setvarnested1={a: {b: newMap()}};nested1.a.b.set("c",{"d": 100})varnested2=iassign(nested1,(m,ctx)=>m.a.b.get("c"),(c)=>{c.e=200;returnc;});
Activity
#12 iassign does not work correctly with ES6 Map
engineforce commentedon Jun 22, 2017
ES6 Map support is added in 1.0.36, please refer to example 9.
Note: even with the fix, getProp() won't be able to handle navigate into the map object, it only supports navigate upto the map object. E.g.,
engineforce commentedon Jun 22, 2017
Regarding to set the useConstructor Option in every file (after import), can you create a git repo that can reproduce the bug?