Update 08.1-more-about-refs.md
Iurii Kucherov committed
Dec 1, 2015 at 19:28 UTC
36dfe62f68e6dd461ca1555dee0d77c771b3e841
1 file changed
+1
-1
docs/docs/08.1-more-about-refs.md
+1
-1
@@ -5,7 +5,7 @@ permalink: more-about-refs.html
5
prev: working-with-the-browser.html
6
next: tooling-integration.html
7
---
8
-After building your component, you may find yourself wanting to "reach out" and invoke methods on component instances returned from `render()`. In most cases, this should be unnecessary because the reactive data flow always ensures that the most recent props are sent to each child that is output from render(). However, there are a few cases where it still might be necessary or beneficial, so React provides an escape hatch known as `refs`. These `refs` (references) are especially useful when you need to: find the DOM markup rendered by a component (for instance, to position it absolutely), use React components in a larger non-React application, or transition your existing codebase to React.
8
+After building your component, you may find yourself wanting to "reach out" and invoke methods on component instances returned from `render()`. In most cases, this should be unnecessary because the reactive data flow always ensures that the most recent props are sent to each child that is output from `render()`. However, there are a few cases where it still might be necessary or beneficial, so React provides an escape hatch known as `refs`. These `refs` (references) are especially useful when you need to: find the DOM markup rendered by a component (for instance, to position it absolutely), use React components in a larger non-React application, or transition your existing codebase to React.
9
10
Let's look at how to get a ref, and then dive into a complete example.
11