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: contributor-docs/behaviors.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ Generic behaviors provide functionality that is not specific to any single compo
44
44
45
45
### Examples
46
46
47
-
-`useProvidedRefOrCreate`
47
+
-`useCombinedRefs`
48
48
-`usePosition`
49
49
-`useClickAway`
50
50
-`useTypeAhead`
@@ -123,7 +123,7 @@ There are no restrictions on return values of generic behavior hooks. In fact, s
123
123
124
124
- Often, a behavior will need to act on a real DOM element.
125
125
- In this case, the hook should return a ref as part of the returned props for that element. The ref will get spread onto the element, giving the ref access to it.
126
-
- Whenever you need a ref, it must be accepted as an optional setting to the hook. The hook then uses the `useProvidedRefOrCreate` hook to resolve a usable ref. Remember to return the resulting ref from the hook.
126
+
- Whenever you need a ref, it must be accepted as an optional setting to the hook.
0 commit comments