Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Difference between React Component and React Element

What is the difference between React Component and React Element? The documentation mentions both but does not go into detail, some methods require components, other elements...

like image 464
Hoffmann Avatar asked Jun 22 '15 02:06

Hoffmann


People also ask

What is the difference between element and component?

There is certainly a difference between elements and components. Furthermore, a component refers to a small part of a larger entity that mostly is a manufactured object. In contrast, an element is one the simplest parts of which anything consists of.

Is a React component A React element?

While a React component is declared once, it can be used multiple times as a React element in JSX. When it is used, it becomes an instance of the component and lives in React's component tree.

What are elements in React?

Elements are the smallest building blocks of React apps. An element describes what you want to see on the screen: const element = <h1>Hello, world</h1>; Unlike browser DOM elements, React elements are plain objects, and are cheap to create. React DOM takes care of updating the DOM to match the React elements.

How many elements does a React component?

In react component, we can return only one element.


1 Answers

There are three related kinds of thing involved here, with their own names:

  • Components
  • Component instances
  • Elements

This is slightly surprising, since if you're used to other UI frameworks you might expect that there'd only be two kinds of thing, roughly corresponding to classes (like Widget) and instances (like new Widget()). That's not the case in React; component instances are not the same thing as elements, nor is there a one-to-one relationship between them. To illustrate this, consider this code:

import React from 'react'; import ReactDOM from 'react-dom'; import './index.css';  class MyComponent extends React.Component {   constructor(props) {     super(props);     console.log('This is a component instance:', this);   }    render() {     const another_element = <div>Hello, World!</div>;     console.log('This is also an element:', another_element);     return another_element;   } }  console.log('This is a component:', MyComponent)  const element = <MyComponent/>;  console.log('This is an element:', element);  ReactDOM.render(   element,   document.getElementById('root') ); 

In the code above:

  • MyComponent (the class itself) is a Component
  • element is an Element. It's not an instance of MyComponent; rather, it's simply a description of the component instance to be created. It's an object with key, props, ref and type properties. Here, key and ref are null, props is an empty object, and type is MyComponent.
  • An instance of MyComponent gets created (and, in the example above, logs itself from its constructor) when element gets rendered.
  • another_element is also an element, and has key, ref, props and type properties just like element does - but this time the value of type is the string "div".

The design reasons why React has these three distinct concepts are explored in detail in the React team's blog post React Components, Elements, and Instances, which I recommend reading.

Finally, it should be noted that while the official docs are rigorous about using the term "component" to refer to a function or class and "component instance" to refer to an instance, other sources do not necessarily adhere to this terminology; you should expect to see "component" used (incorrectly) to mean "component instance" when reading Stack Overflow answers or discussions on GitHub.

like image 82
Mark Amery Avatar answered Oct 02 '22 16:10

Mark Amery