reatom
monocle-ts
Our great sponsors
reatom | monocle-ts | |
---|---|---|
2 | 7 | |
949 | 1,016 | |
- | - | |
9.7 | 0.0 | |
3 days ago | over 1 year ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
reatom
-
Is redux and thunks still used or are there other alternatives for it now?
Nanostores and Reatom are also great, fast atomic libs
-
Why is it so difficult to modify a deeply nested state in React?
Nice one, really! https://github.com/artalar/reatom
monocle-ts
-
Deep Cloning Objects in JavaScript, the Modern Way
Instead of the "deep path properties" syntax, you might want to take the opportunity to learn about functional lenses with monocle-ts
https://gcanti.github.io/monocle-ts/
-
I may have a crush on the TypeScript compiler, because of stuff like this
You may be interested also in checking out the implementation of Lens in monocle-ts, one of the libraries in the fp-ts ecosystem
-
Haskell Lens Tutorial by Exercises
For anyone - anyone who's faffed around with JavaScript's spread syntax when working with nested immutable data, anyway - struggling to understand the general concept or utility of lenses, I'd encourage looking into monocle-ts. The motivation [0] that kicks off the README instantly made me a believer, and TypeScript's idiosyncratic type system makes using the library remarkably natural; it fits right in without needing to deal with anything analogous to Template Haskell.
[0] https://github.com/gcanti/monocle-ts#motivation
-
Is there a cleaner way to immutably update a deeply nested attribute? (I feel like this is not very clean)
You could have a look at the monocle-ts library. It was designed to deal with this kind of problem.
-
Simple Immutable Data w/ Spectacles π
spectacles-ts integrates seamlessly with the fp-ts ecosystem (it's built on top of the excellent monocle-ts library)
-
Why is it so difficult to modify a deeply nested state in React?
lenses help with this quite a bit, check out monocle-ts
-
You could have invented lenses!
You notice that Getters are composable as they are just pure functions, but the fact that setters are mutating values is not that nice. Tho, at this point we have invented quasi mutable lenses and If you really want you might invent actual purely functional lenses as well, but thatβs for another day. Meanwhile you can take a look at an actual typescript lesses library from @gcanti / monocle-ts.
What are some alternatives?
zustand - π» Bear necessities for state management in React
optics-ts - Type-safe, ergonomic, polymorphic optics for TypeScript
jotai - π» Primitive and flexible state management for React
valtio - π Valtio makes proxy-state simple for React and Vanilla
spectacles-ts - Practical Optics β’ Unfancy monocle-ts
zedux - :zap: A Molecular State Engine for React
immutability-helper - mutate a copy of data without changing the original source
nanostores - A tiny (286 bytes) state manager for React/RN/Preact/Vue/Svelte with many atomic tree-shakable stores
fp-ts-contrib - A community driven utility package for fp-ts
resso - πͺ’ The simplest React state manager