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
You see, since all "modifying" methods return a new object, ImmutableJS creates a new one internally, which is, obviously, isn't proxied!
This bugs totally destroys a potential use of this package, unfortunately. It's just a tip of the scale, the problem exists in any collection methods which return a new object!
The text was updated successfully, but these errors were encountered:
This was never fully thought out, so there's going to have to be changes to support filtering and other array methods. It's been a while since I messed with this.
As far as I see, you didn't actually get to using this project yourself, did you? :) Were there any specific issues why you chose not to? Or did you stopped using Immutable.js at all? I would glad to hear more on that, so I would know whether to spend more time on this or not in future.
Hi!
I see that
List
's property length is proxied to becomesize
which is the right one for Immutable.Here's a piece of code:
You see, since all "modifying" methods return a new object, ImmutableJS creates a new one internally, which is, obviously, isn't proxied!
This bugs totally destroys a potential use of this package, unfortunately. It's just a tip of the scale, the problem exists in any collection methods which return a new object!
The text was updated successfully, but these errors were encountered: