4 ms·
Try MobX. I think it's the holy grail of state management. You have your app state in an object/class, and components automatically rerender when the part of t
by hombre_fatal 2y ago
Try MobX. I think it's the holy grail of state management.
You have your app state in an object/class, and components automatically rerender when the part of the store changes that they access during render.
class Store {
counter = 0
constructor() { makeAutoObservable(this) }
increment() { this.counter++ }
}
const Component = observer(() {
const store = useStore()
const click = () => store.increment())
return <button onClick={click}>{store.counter}</button>
})
It has a very light set of idiosyncrasies for what it gives you unlike, say, redux.
- Rohansi 2y agoThat looks pretty good! I actually implemented my own state management that works like that five years ago because I didn't like the options at the time. https://github.com/Facepunch/react-class-model https://github.com/Facepunch/react-class-model (note: context is not required)