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
Reliably handles all state outside API interactions
GraphQL clients have evolved rapidly and in my own projects I pretty much use them for all interactions except for primitive components and some parts of the feature that data should prioritize local more than API
I noticed that there have been increased number of headless ui libraries, but quite some of them do not handle logics at all. See if this library can solve this
Ideas
Remove immer from dependency
Immer is nice, but not a necessary dependency for this library to fulfill its goal
Can store state machine alongside data
State machine is useful in UI specific logics since same action should do different stuff under different context. An example would be triggering a "type something" action in edit mode vs readonly mode. Note that a single state is often not that useful since you can be in a stage of edit mode or maybe syncing in collaboration mode in parallel. Tried xstate before but it's pretty painful
Tasks
Handle Atom in atom and non-atom in useAtom
Fix dispose effect for react (Currenly use workaround by forcererender on dispose)
rename effect to watch and add usewatch Keep effect and use useSideEffect instead
Support wrapping atom and useAtom over-and-over again
Add batch update
Should error if batch level goes too high, because it's probably due to infinite loop
Fix currentObserver must use settimeout when unassign in react effect (Actually this kind of make sense since need a render cycle to collect the dependencies?)
Might be that the effect in useatom is not actually wrapping the scope of atom effect?
What reim should aim to be
Reliably handles all state outside API interactions
GraphQL clients have evolved rapidly and in my own projects I pretty much use them for all interactions except for primitive components and some parts of the feature that data should prioritize local more than API
I noticed that there have been increased number of headless ui libraries, but quite some of them do not handle logics at all. See if this library can solve this
Ideas
Remove
immer
from dependencyImmer is nice, but not a necessary dependency for this library to fulfill its goal
Can store state machine alongside data
State machine is useful in UI specific logics since same action should do different stuff under different context. An example would be triggering a "type something" action in edit mode vs readonly mode. Note that a single state is often not that useful since you can be in a stage of edit mode or maybe syncing in collaboration mode in parallel. Tried xstate before but it's pretty painful
Tasks
rename effect to watch and add usewatchKeepeffect
and useuseSideEffect
insteadcurrentObserver
must use settimeout when unassign in react effect (Actually this kind of make sense since need a render cycle to collect the dependencies?)useAtom
e.g.
The text was updated successfully, but these errors were encountered: