Every JS value is technically mutable, but using Immutable.js's set() and update() functions would make copies with changes applied, just as they do for Immutable.js's own collections.
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
No need to ever unfreeze during set() and update() since those return persistent copies with changes applied. Unfortunately Object.freeze() is still quite slow.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Will the nested objects be immutable?
-
Every JS value is technically mutable, but using Immutable.js's set()/setIn() and update()/updateIn() functions would make copies of plain JS objs with changes applied, just as they already do for Immutable.js's own collections.
- Još 2 druga odgovora
Novi razgovor -
-
-
Neat stuff. Have you seen what
@colbyrabideau did with https://github.com/HubSpot/transmute/blob/master/README.md …? -
I haven't seen that, but it looks great! Looks like confirmation this is a good idea
- Još 3 druga odgovora
Novi razgovor -
-
-
We wrote our own functional getIn, very similar to what you’re proposing. It’s been super helpful. setIn would be awesome too.
-
Using flow/typescript by chance? Getting the right types makes them so much more useful, but that might be the hardest part.
- Još 3 druga odgovora
Novi razgovor -
-
-
maybe unrelated? https://github.com/nathanmarz/specter …
-
Seems like a cool clojure lib, but a bit beyond the scope of what I'm proposing in the PR above.
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.