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
The atom one starts in loading state and only resolves after a second.
I'd expect the promise returned from getPromise(oneAtom) to be initially pending (which it does) and eventually resolve with the value of the atom one when that one resolves. However, the returned promise remains in pending state forever; neither the then nor the catch callback are ever called.
Note that I've intentionally omitted the cleanup logic for setTimeout to keep the example concise.
The text was updated successfully, but these errors were encountered:
Consider the following scenario where an atom effect tries to get the value of another atom.
The atom
one
starts in loading state and only resolves after a second.I'd expect the promise returned from
getPromise(oneAtom)
to be initially pending (which it does) and eventually resolve with the value of the atomone
when that one resolves. However, the returned promise remains in pending state forever; neither thethen
nor thecatch
callback are ever called.Note that I've intentionally omitted the cleanup logic for
setTimeout
to keep the example concise.The text was updated successfully, but these errors were encountered: