Skip to content

Bailing out doesn't work properly in lazy components with default props #17151

Closed
@jddxf

Description

@jddxf

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
Bailing out doesn't work properly in lazy components with default props. It seems we're incorrectly comparing unresolved props (oldProps) with resolved props (newProps).

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:
https://codesandbox.io/s/stoic-curran-3otbb

What is the expected behavior?
In the example above, componentDidUpdate shouldn't have been called when the button is clicked.

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions