Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Why are React props immutable?

I've been reading React's Quick Start documentation;

Whether you declare a component as a function or a class, it must never modify its own props

This is a "pure" function, because it doesn't attempt to change its inputs, and always returns the same result for the same inputs:

function sum(a, b) {
  return a + b;
}

This in an "impure" function, because it changes its own input: https://codesandbox.io/s/9z38xv4x7r

function SayHi(props) {
  props.name = "Jim"; // TypeError Cannot assign to read only property 'name' of object '#<Object>'
  return <h1>Hi {props.name}!</h1>;
}

Why are React props read-only?

like image 339
dǝɥɔS ʇoıןןƎ Avatar asked Nov 24 '17 10:11

dǝɥɔS ʇoıןןƎ


People also ask

Why is React state immutable?

Why Immer works well for React State Immutability? In React, using an Immutable state enables quick and cheap comparison of the state tree before and after a change. As a result, each component decides whether to re-rendered or not before performing any costly DOM operations.

Is state and props both are immutable?

Props are immutable. State is mutable. 3. Props allow you to pass data from one component to other components as an argument.

Is React elements are immutable?

React elements are immutable. Once you create an element, you can't change its children or attributes.


2 Answers

A component should manage its own state, but it should not manage its own props. props is essentially "state that is managed by the component owner." That's why props are immutable.

React docs also recommends to treat state as if it's immutable. That is because by manipulating this.state directly you are circumventing React’s state management, which can be potentially dangerous as calling setState() afterwards may replace the mutation you made.

like image 82
Shubham Khatri Avatar answered Sep 19 '22 09:09

Shubham Khatri


You may think of React component as a function of its props and state. As you advance through the docs, you'll find that this is the case, as most functions in the React component life cycle have signatures of the form (prop, state) => { //code }.

React docs define props as any arbitrary input given to a component, and the component will render something based on the props ( and sometimes based on state too, if it is a stateful component ). So props is like something that is given to the component for say, reference. Imagine it this way: you are a component, and your parent component gives you a reference book, containing some rules on how you must behave ( a.k.a. render ). Two cases may arise:

  1. You are dumb (stateless): You just read the book, and behave so.
  2. You are smart (stateful): You read the book, and then note some things in your notepad, that you may view, update or delete. You may even take copy down content from the book to your notepad, and then edit the notepad.

Either way, you may not update the reference book given to you. Only the parent component can update it ( example, give you another book, or change its content ).

I don't know if this is a correct representation, but React components work in a similar way. You'll get the hang of it soon. Make sure you read Thinking in React too. Happy coding!

like image 34
Dane Avatar answered Sep 20 '22 09:09

Dane