Using Props to Initialize State of Component

Evan Hicks

—July 12, 2022

The Problem

Where the props are used to set the initial state of the Component is a general anti-pattern of React. This implies that the state of the component is tied to the props of the component. The issue with doing this is that the constructor is only ever called once in the life cycle of the component. Since the props can change many times during that lifecycle, that implication is broken.

Click to Copy

class MyComponent extends Component {
    constructor(props) {
        super(props)
        this.state = {
            name: props.name,
        }
    }
}

The Solution

This is an anti-pattern that should be avoided, and the state should be updated in the componentWillReceiveProps lifecycle method instead. That way the state and the props can stay in step with each other.

Click to Copy

class MyComponent extends Component {
    constructor(props) {
        super(props)
        this.state = {
            name: "",
        }
    }

    componentWillReceiveProps(props) {
        this.setState({
            name: props.name,
        })
    }
}

This pattern can be used if the props are explicitly meant to initialize the state once, and after that the component will manage its own state.

Platform

Languages & Frameworks

Why Sentry?

Features

Using Props to Initialize State of Component

The Problem

The Solution

Further Reading

Using Props to Initialize State of Component

The Solution

Further Reading

A peek at your privacy

Who we collect PII from

PII we may collect about you

How we use your PII

Third parties who receive your PII

We use cookies (but not for advertising)

Know your rights