{"componentChunkName":"component---src-templates-docs-js","path":"/docs/forwarding-refs.html","result":{"data":{"markdownRemark":{"html":"

Ref forwarding is a technique for automatically passing a ref through a component to one of its children. This is typically not necessary for most components in the application. However, it can be useful for some kinds of components, especially in reusable component libraries. The most common scenarios are described below.

\n

Forwarding refs to DOM components

\n

Consider a FancyButton component that renders the native button DOM element:\n

\n 
function FancyButton(props) {\n  return (\n    <button className=\"FancyButton\">\n      {props.children}\n    </button>\n  );\n}
\n

\n

React components hide their implementation details, including their rendered output. Other components using FancyButton usually will not need to obtain a ref to the inner button DOM element. This is good because it prevents components from relying on each other’s DOM structure too much.

\n

Although such encapsulation is desirable for application-level components like FeedStory or Comment, it can be inconvenient for highly reusable “leaf” components like FancyButton or MyTextInput. These components tend to be used throughout the application in a similar manner as a regular DOM button and input, and accessing their DOM nodes may be unavoidable for managing focus, selection, or animations.

\n

Ref forwarding is an opt-in feature that lets some components take a ref they receive, and pass it further down (in other words, “forward” it) to a child.

\n

In the example below, FancyButton uses React.forwardRef to obtain the ref passed to it, and then forward it to the DOM button that it renders:

\n

\n 
const FancyButton = React.forwardRef((props, ref) => (  <button ref={ref} className=\"FancyButton\">    {props.children}\n  </button>\n));\n\n// You can now get a ref directly to the DOM button:\nconst ref = React.createRef();\n<FancyButton ref={ref}>Click me!</FancyButton>;
\n

\n

This way, components using FancyButton can get a ref to the underlying button DOM node and access it if necessary—just like if they used a DOM button directly.

\n

Here is a step-by-step explanation of what happens in the above example:

\n
    \n
  1. We create a React ref by calling React.createRef and assign it to a ref variable.
    2. \n
  2. We pass our ref down to <FancyButton ref={ref}> by specifying it as a JSX attribute.
    3. \n
  3. React passes the ref to the (props, ref) => ... function inside forwardRef as a second argument.
    4. \n
  4. We forward this ref argument down to <button ref={ref}> by specifying it as a JSX attribute.
    5. \n
  5. When the ref is attached, ref.current will point to the <button> DOM node.
    6. \n
\n
\n

Note

\n

The second ref argument only exists when you define a component with React.forwardRef call. Regular function or class components don’t receive the ref argument, and ref is not available in props either.

\n

Ref forwarding is not limited to DOM components. You can forward refs to class component instances, too.

\n
\n

Note for component library maintainers

\n

When you start using forwardRef in a component library, you should treat it as a breaking change and release a new major version of your library. This is because your library likely has an observably different behavior (such as what refs get assigned to, and what types are exported), and this can break apps and other libraries that depend on the old behavior.

\n

Conditionally applying React.forwardRef when it exists is also not recommended for the same reasons: it changes how your library behaves and can break your users’ apps when they upgrade React itself.

\n

Forwarding refs in higher-order components

\n

This technique can also be particularly useful with higher-order components (also known as HOCs). Let’s start with an example HOC that logs component props to the console:\n

\n 
function logProps(WrappedComponent) {  class LogProps extends React.Component {\n    componentDidUpdate(prevProps) {\n      console.log('old props:', prevProps);\n      console.log('new props:', this.props);\n    }\n\n    render() {\n      return <WrappedComponent {...this.props} />;    }\n  }\n\n  return LogProps;\n}
\n

\n

The “logProps” HOC passes all props through to the component it wraps, so the rendered output will be the same. For example, we can use this HOC to log all props that get passed to our “fancy button” component:\n

\n 
class FancyButton extends React.Component {\n  focus() {\n    // ...\n  }\n\n  // ...\n}\n\n// Rather than exporting FancyButton, we export LogProps.\n// It will render a FancyButton though.\nexport default logProps(FancyButton);
\n

\n

There is one caveat to the above example: refs will not get passed through. That’s because ref is not a prop. Like key, it’s handled differently by React. If you add a ref to a HOC, the ref will refer to the outermost container component, not the wrapped component.

\n

This means that refs intended for our FancyButton component will actually be attached to the LogProps component:\n

\n 
import FancyButton from './FancyButton';\n\nconst ref = React.createRef();\n// The FancyButton component we imported is the LogProps HOC.\n// Even though the rendered output will be the same,\n// Our ref will point to LogProps instead of the inner FancyButton component!\n// This means we can't call e.g. ref.current.focus()\n<FancyButton\n  label=\"Click Me\"\n  handleClick={handleClick}\n  ref={ref}/>;
\n

\n

Fortunately, we can explicitly forward refs to the inner FancyButton component using the React.forwardRef API. React.forwardRef accepts a render function that receives props and ref parameters and returns a React node. For example:\n

\n 
function logProps(Component) {\n  class LogProps extends React.Component {\n    componentDidUpdate(prevProps) {\n      console.log('old props:', prevProps);\n      console.log('new props:', this.props);\n    }\n\n    render() {\n      const {forwardedRef, ...rest} = this.props;\n      // Assign the custom prop \"forwardedRef\" as a ref\n      return <Component ref={forwardedRef} {...rest} />;    }\n  }\n\n  // Note the second param \"ref\" provided by React.forwardRef.\n  // We can pass it along to LogProps as a regular prop, e.g. \"forwardedRef\"\n  // And it can then be attached to the Component.\n  return React.forwardRef((props, ref) => {    return <LogProps {...props} forwardedRef={ref} />;  });}
\n

\n

Displaying a custom name in DevTools

\n

React.forwardRef accepts a render function. React DevTools uses this function to determine what to display for the ref forwarding component.

\n

For example, the following component will appear as ”ForwardRef” in the DevTools:

\n

\n 
const WrappedComponent = React.forwardRef((props, ref) => {\n  return <LogProps {...props} forwardedRef={ref} />;\n});
\n

\n

If you name the render function, DevTools will also include its name (e.g. ”ForwardRef(myFunction)”):

\n

\n 
const WrappedComponent = React.forwardRef(\n  function myFunction(props, ref) {\n    return <LogProps {...props} forwardedRef={ref} />;\n  }\n);
\n

\n

You can even set the function’s displayName property to include the component you’re wrapping:

\n

\n 
function logProps(Component) {\n  class LogProps extends React.Component {\n    // ...\n  }\n\n  function forwardRef(props, ref) {\n    return <LogProps {...props} forwardedRef={ref} />;\n  }\n\n  // Give this component a more helpful display name in DevTools.\n  // e.g. \"ForwardRef(logProps(MyComponent))\"\n  const name = Component.displayName || Component.name;  forwardRef.displayName = `logProps(${name})`;\n  return React.forwardRef(forwardRef);\n}
\n

","frontmatter":{"title":"Forwarding Refs","next":null,"prev":null},"fields":{"path":"content/docs/forwarding-refs.md","slug":"docs/forwarding-refs.html"}}},"pageContext":{"slug":"docs/forwarding-refs.html"}},"staticQueryHashes":[]}