Andrew Clark 2ae4c62158 Always set pendingProps to the next props (#11580) ...

In the current implementation, pendingProps is null if there are no new
props since the last commit. When that happens, we bail out and reuse
the current props.

But it makes more sense to always set pendingProps to whatever the next
props will be. In other words, pendingProps is never null: it points to
either new props, or to the current props. Modeling it this way lets us
delete lots of code branches and is easier to reason about bail outs:
just compare the pending props to the current props.

2017-11-28 16:50:23 -08:00

..

events

Add a note about private API dependency for a test

2017-11-24 01:11:24 +00:00

react

Blacklist spyOn(). Add explicit spyOnProd() and spyOnDevAndProd() (#11691)

2017-11-28 14:06:26 -08:00

react-art

Updating package versions for release 16.2.0

2017-11-28 13:26:36 -08:00

react-call-return

Updating package versions for release 16.2.0

2017-11-28 13:26:36 -08:00

react-cs-renderer

Set fragment export flags to true (#11672)

2017-11-27 13:09:15 -08:00

react-dom

root.createBatch (#11473)

2017-11-28 16:48:35 -08:00

react-native-renderer

Move ReactFiberTreeReflection to react-reconciler/reflection (#11683)

2017-11-28 16:57:22 +00:00

react-noop-renderer

Move ReactFiberTreeReflection to react-reconciler/reflection (#11683)

2017-11-28 16:57:22 +00:00

react-reconciler

Always set pendingProps to the next props (#11580)

2017-11-28 16:50:23 -08:00

react-rt-renderer

Move ReactFiberTreeReflection to react-reconciler/reflection (#11683)

2017-11-28 16:57:22 +00:00

react-test-renderer

root.createBatch (#11473)

2017-11-28 16:48:35 -08:00

shared

Updating package versions for release 16.2.0

2017-11-28 13:26:36 -08:00