Skip to content
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.

Fix inconsistent behavior between setState in init and directly assigning to state #232

Merged
merged 4 commits into from
Aug 14, 2019
Merged

Fix inconsistent behavior between setState in init and directly assigning to state #232

merged 4 commits into from
Aug 14, 2019

Commits on Aug 13, 2019

  1. Update initial mount of stateful components to run getDerivedStateFro… 

    …mProps after init
    @ZoteTheMighty
    ZoteTheMighty committed Aug 13, 2019
    Configuration menu
    Copy the full SHA
    3930dbd View commit details
    Browse the repository at this point in the history

  2. Add test to verify new behavior

    @ZoteTheMighty
    ZoteTheMighty committed Aug 13, 2019
    Configuration menu
    Copy the full SHA
    412f685 View commit details
    Browse the repository at this point in the history

  3. Update changelog

    @ZoteTheMighty
    ZoteTheMighty committed Aug 13, 2019
    Configuration menu
    Copy the full SHA
    f9ac700 View commit details
    Browse the repository at this point in the history

Commits on Aug 14, 2019

  1. Removed unneccsary assignment of result of 'assign'

    @ZoteTheMighty
    ZoteTheMighty committed Aug 14, 2019
    Configuration menu
    Copy the full SHA
    409cc64 View commit details
    Browse the repository at this point in the history