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
Copy file name to clipboardExpand all lines: docs/reference/faq.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,4 +12,7 @@ route: '/reference/faq'
12
12
13
13
### Why do I need to use `result.current` instead of just `result`?
14
14
15
-
The "ref-like" representation of the hook's result allows the value to be updated when the hook gets rerendered, whether that be from calling `rerender`, calling a callback returned from the hook, or an asynchronous action triggered by executing the hook. Without `current` the library would have to provide some way of requesting the updated values for assertions.
15
+
The "ref-like" representation of the hook's result allows the value to be updated when the hook gets
16
+
rerendered, whether that be from calling `rerender`, calling a callback returned from the hook, or
17
+
an asynchronous action triggered by executing the hook. Without `current` the library would have to
18
+
provide some way of requesting the updated values for assertions.
0 commit comments