Fix typo (#9786)
Max Donchenko committed
May 26, 2017 at 14:37 UTC
43f2ea079cf18a3b5301fc4f02bcdf987e00020c
1 file changed
+1
-1
docs/docs/refs-and-the-dom.md
+1
-1
@@ -149,7 +149,7 @@ function CustomTextInput(props) {
149
150
In rare cases, you might want to have access to a child's DOM node from a parent component. This is generally not recommended because it breaks component encapsulation, but it can occasionally be useful for triggering focus or measuring the size or position of a child DOM node.
151
152
-While you could [add a ref to to the child component](#adding-a-ref-to-a-class-component), this is not an ideal solution, as you would only get a component instance rather than a DOM node. Additionally, this wouldn't work with functional components.
152
+While you could [add a ref to the child component](#adding-a-ref-to-a-class-component), this is not an ideal solution, as you would only get a component instance rather than a DOM node. Additionally, this wouldn't work with functional components.
153
154
Instead, in such cases we recommend exposing a special prop on the child. The child would take a function prop with an arbitrary name (e.g. `inputRef`) and attach it to the DOM node as a `ref` attribute. This lets the parent pass its ref callback to the child's DOM node through the component in the middle.
155