Brian Vaughn 4eed18dd72 Invoke both legacy and UNSAFE_ lifecycles when both are present (#12134) ...

* Invoke both legacy and UNSAFE_ lifecycles when both are present

This is to support edge cases with eg create-react-class where a mixin defines a legacy lifecycle but the component being created defines an UNSAFE one (or vice versa).

I did not warn about this case because the warning would be a bit redundant with the deprecation warning which we will soon be enabling. I could be convinced to change my stance here though.

* Added explicit function-type check to SS ReactPartialRenderer

2018-02-01 11:15:57 -08:00

..

events

Interactive updates (#12100)

2018-01-29 23:49:10 -08:00

react

Invoke both legacy and UNSAFE_ lifecycles when both are present (#12134)

2018-02-01 11:15:57 -08:00

react-art

Sync scheduling by default, with an async opt-in (#11771)

2018-01-08 18:50:02 -08:00

react-call-return

Debug render-phase side effects in "strict" mode (#12094)

2018-01-25 14:30:53 -08:00

react-dom

Invoke both legacy and UNSAFE_ lifecycles when both are present (#12134)

2018-02-01 11:15:57 -08:00

react-native-renderer

Interactive updates (#12100)

2018-01-29 23:49:10 -08:00

react-noop-renderer

Interactive updates (#12100)

2018-01-29 23:49:10 -08:00

react-reconciler

Invoke both legacy and UNSAFE_ lifecycles when both are present (#12134)

2018-02-01 11:15:57 -08:00

react-test-renderer

Invoke both legacy and UNSAFE_ lifecycles when both are present (#12134)

2018-02-01 11:15:57 -08:00

shared

Switch to JSX API for context (#12123)

2018-01-30 13:06:12 -08:00