Skip to content

problem with getInitialState returning null #883

@chenglou

Description

@chenglou

Right now it's accepted to return null from getInitialState, but if a mixin also defines a getInitialState, and if one of the two returns null then the merge throws an error when trying to merge an object with null. What should be the correct behavior here?

@cpojer

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions