From b2aa4d143fd11c9c72d577d38724dddf1c37352b Mon Sep 17 00:00:00 2001 From: Sunny Ripert Date: Thu, 2 Mar 2017 20:57:58 +0100 Subject: [PATCH] Fix spacing in documentation (#9070) Replace non-breaking space by space. (cherry picked from commit 179240ca3013878059cc1d8b43e31e929a7bc428) --- docs/docs/refs-and-the-dom.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/refs-and-the-dom.md b/docs/docs/refs-and-the-dom.md index eaf19e7b39..85a0429eb4 100644 --- a/docs/docs/refs-and-the-dom.md +++ b/docs/docs/refs-and-the-dom.md @@ -145,7 +145,7 @@ function CustomTextInput(props) { Your first inclination may be to use refs to "make things happen" in your app. If this is the case, take a moment and think more critically about where state should be owned in the component hierarchy. Often, it becomes clear that the proper place to "own" that state is at a higher level in the hierarchy. See the [Lifting State Up](/react/docs/lifting-state-up.html) guide for examples of this. -### Legacy API: String Refs +### Legacy API: String Refs If you worked with React before, you might be familiar with an older API where the `ref` attribute is a string, like `"textInput"`, and the DOM node is accessed as `this.refs.textInput`. We advise against it because string refs have [some issues](https://github.com/facebook/react/pull/8333#issuecomment-271648615), are considered legacy, and **are likely to be removed in one of the future releases**. If you're currently using `this.refs.textInput` to access refs, we recommend the callback pattern instead.