{"componentChunkName":"component---src-templates-docs-js","path":"/docs/composition-vs-inheritance.html","result":{"data":{"markdownRemark":{"html":"

React has a powerful composition model, and we recommend using composition instead of inheritance to reuse code between components.

\n

In this section, we will consider a few problems where developers new to React often reach for inheritance, and show how we can solve them with composition.

\n

Containment

\n

Some components don’t know their children ahead of time. This is especially common for components like Sidebar or Dialog that represent generic “boxes”.

\n

We recommend that such components use the special children prop to pass children elements directly into their output:

\n
function FancyBorder(props) {\n  return (\n    <div className={'FancyBorder FancyBorder-' + props.color}>\n      {props.children}    </div>\n  );\n}
\n

This lets other components pass arbitrary children to them by nesting the JSX:

\n
function WelcomeDialog() {\n  return (\n    <FancyBorder color=\"blue\">\n      <h1 className=\"Dialog-title\">        Welcome      </h1>      <p className=\"Dialog-message\">        Thank you for visiting our spacecraft!      </p>    </FancyBorder>\n  );\n}
\n

Try it on CodePen

\n

Anything inside the <FancyBorder> JSX tag gets passed into the FancyBorder component as a children prop. Since FancyBorder renders {props.children} inside a <div>, the passed elements appear in the final output.

\n

While this is less common, sometimes you might need multiple “holes” in a component. In such cases you may come up with your own convention instead of using children:

\n
function SplitPane(props) {\n  return (\n    <div className=\"SplitPane\">\n      <div className=\"SplitPane-left\">\n        {props.left}      </div>\n      <div className=\"SplitPane-right\">\n        {props.right}      </div>\n    </div>\n  );\n}\n\nfunction App() {\n  return (\n    <SplitPane\n      left={\n        <Contacts />      }\n      right={\n        <Chat />      } />\n  );\n}
\n

Try it on CodePen

\n

React elements like <Contacts /> and <Chat /> are just objects, so you can pass them as props like any other data. This approach may remind you of “slots” in other libraries but there are no limitations on what you can pass as props in React.

\n

Specialization

\n

Sometimes we think about components as being “special cases” of other components. For example, we might say that a WelcomeDialog is a special case of Dialog.

\n

In React, this is also achieved by composition, where a more “specific” component renders a more “generic” one and configures it with props:

\n
function Dialog(props) {\n  return (\n    <FancyBorder color=\"blue\">\n      <h1 className=\"Dialog-title\">\n        {props.title}      </h1>\n      <p className=\"Dialog-message\">\n        {props.message}      </p>\n    </FancyBorder>\n  );\n}\n\nfunction WelcomeDialog() {\n  return (\n    <Dialog      title=\"Welcome\"      message=\"Thank you for visiting our spacecraft!\" />  );\n}
\n

Try it on CodePen

\n

Composition works equally well for components defined as classes:

\n
function Dialog(props) {\n  return (\n    <FancyBorder color=\"blue\">\n      <h1 className=\"Dialog-title\">\n        {props.title}\n      </h1>\n      <p className=\"Dialog-message\">\n        {props.message}\n      </p>\n      {props.children}    </FancyBorder>\n  );\n}\n\nclass SignUpDialog extends React.Component {\n  constructor(props) {\n    super(props);\n    this.handleChange = this.handleChange.bind(this);\n    this.handleSignUp = this.handleSignUp.bind(this);\n    this.state = {login: ''};\n  }\n\n  render() {\n    return (\n      <Dialog title=\"Mars Exploration Program\"\n              message=\"How should we refer to you?\">\n        <input value={this.state.login}               onChange={this.handleChange} />        <button onClick={this.handleSignUp}>          Sign Me Up!        </button>      </Dialog>\n    );\n  }\n\n  handleChange(e) {\n    this.setState({login: e.target.value});\n  }\n\n  handleSignUp() {\n    alert(`Welcome aboard, ${this.state.login}!`);\n  }\n}
\n

Try it on CodePen

\n

So What About Inheritance?

\n

At Facebook, we use React in thousands of components, and we haven’t found any use cases where we would recommend creating component inheritance hierarchies.

\n

Props and composition give you all the flexibility you need to customize a component’s look and behavior in an explicit and safe way. Remember that components may accept arbitrary props, including primitive values, React elements, or functions.

\n

If you want to reuse non-UI functionality between components, we suggest extracting it into a separate JavaScript module. The components may import it and use that function, object, or a class, without extending it.

","frontmatter":{"title":"Composition vs Inheritance","next":"thinking-in-react.html","prev":"lifting-state-up.html"},"fields":{"path":"content/docs/composition-vs-inheritance.md","slug":"docs/composition-vs-inheritance.html"}}},"pageContext":{"slug":"docs/composition-vs-inheritance.html"}},"staticQueryHashes":[]}