Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 4ff8ffc

Browse files
committed
Fixed FAQ question title
1 parent 39add3b commit 4ff8ffc

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

‎docs/reference/faq.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,10 @@ route: '/reference/faq'
66

77
# Frequently Asked Questions
88

9-
- [Why I need to use `result.current` instead of just `result`?](/reference/faq#why-i-need-to-use-resultcurrent-instead-of-just-result)
9+
- [Why do I need to use `result.current` instead of just `result`?](/reference/faq#why-do-i-need-to-use-resultcurrent-instead-of-just-result)
1010

1111
---
1212

13-
### Why I need to use `result.current` instead of just `result`?
13+
### Why do I need to use `result.current` instead of just `result`?
1414

1515
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.

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /