Is it good practice to have a child with constructor and its own state in React JS? Or should props be used in this case?

Question

I have a child component that is getting rendered on App.js (parent) with its own state as it is not dependent on the parent state. Is this good practice? Or should props be used?

It depends on specific case. – Estus Flask Feb 10 '19 at 16:54 — Estus Flask, Feb 10 '19 at 16:54

score 0 · Answer 1 · answered Feb 10 '19 at 16:37

0

The React documentation describes the process of Lifting State Up in which they suggest that indeed, as a general practice, state should be lifted up (e.g., into the parent) and given to children as props.

answered Feb 10 '19 at 16:37

T.J. Crowder

1,031,962
187
1,923
1,875

score 0 · Accepted Answer · answered Feb 10 '19 at 20:04

It really depends on what the use of your child component is. If the component only uses a few props to render, there is no use for a class based component with its own state. If the component needs more functionality (states etc) you are better of using a class based component.

Also, if your component have a few child components which are dependent on their parent it could be appropriate using state.

I think this question is relevant to what you are asking.

Is it good practice to have a child with constructor and its own state in React JS? Or should props be used in this case?

2 Answers2