jotai
jotai copied to clipboard
👻 Primitive and flexible state management for React
Docs for new `atomWithDebounce` atom creator as discussed here: https://github.com/pmndrs/jotai/discussions/553#discussioncomment-3354600
Hello! Creating this issue as a clean & centralized document for problems related to react-query, without the need of reading through all the issues titles. The intention is to find...
This PR includes: - [x] #1116 - [x] #1273 - [ ] #1286
ref: https://twitter.com/dai_shi/status/1513173028674617350 core doesn't depend on `AbortController`, only the one in utils does. - [x] impl - [ ] tests (does it work if an error is thrown?) - [...
This is just a naive merge and there should be room for improvement. This is also meaningful with other activities. - docs/basics/getting-started.mdx @sandren - docs/basics/mental-model.mdx @TwistedMinda #1212
When using `atomWithHash` or `atomWithReset` it would be nice if the state setter function would also accept the `RESET` symbol as return type. ## Problem Suppose I want to encode...
When using `atomWithStorage` with large objects it's common to add new fields later in development. Unfortunately even if I provide default value in `initialValue` object this is ignored as `initialValue`...
A quick change as discussed on chat to clarify that `useSetAtom()` is useful in general as a performance improvement.
Found some issues while developing #837: - [x] Ignore snapshots with invalidated atoms - [ ] Avoid extra re-renders - [x] Maybe we should somehow return `dependents` too. (Provider's useDebugState...
Task: invalidating atoms in #911 Tries to ignore the snapshots of invalidated atoms, as inspired by useAtomsDevtools!