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
{{ message }}
This repository has been archived by the owner on Mar 19, 2024. It is now read-only.
I've read some issues on this on other repositories and it seems that we do not need to do any further work.
A "ref" is suppose to be just house a pointer to something. While we traditionally use it for DOM references on a given React Element, it seems like it will be used for any asynchronous value.
I'll leave this issue around for a bit longer but it might not entail any future technical work besides some more concrete research.
You're right, assuming Element is short-sighted. This became more clear for me with hooks, because the useRef hook is really nice for dealing with callback functions and timeout ids.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
604c752
The text was updated successfully, but these errors were encountered: