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
As discussed, our preference is to make use of React Query directly, rather using it via a wrapper library specific to Jotai.
Results in
Being less tied to a state management library
Having a simpler state set up, with fewer atom chains
Fewer protocol-level side effects being triggered implicitly
To the greatest extent possible, we should try and remove as many atoms as possible. Using the newly-created hooks to pass API data into components that need it, and thus removing the chained atom dependencies.
As discussed, our preference is to make use of React Query directly, rather using it via a wrapper library specific to Jotai.
Results in
To the greatest extent possible, we should try and remove as many atoms as possible. Using the newly-created hooks to pass API data into components that need it, and thus removing the chained atom dependencies.
Query atoms
networkOnlineStatusState
#1803namesResponseState
#1801accountMempoolTransactionsUnanchoredClient
#1938contractSourceResponseState
#1829contractInterfaceResponseState
#1830accountInfoUnanchoredClient
#1811accountBalancesAnchoredClient
accountBalancesUnanchoredClient
accountTransactionsUnanchoredClient
When picking one of these, create an issue for it so we can track them individually.
The text was updated successfully, but these errors were encountered: