react/packages/react-noop-renderer
Andrew Clark 4fe6eec15b
Always batch updates of like priority within the same event (#13071)
Expiration times are computed by adding to the current time (the start
time). However, if two updates are scheduled within the same event, we
should treat their start times as simultaneous, even if the actual clock
time has advanced between the first and second call.

In other words, because expiration times determine how updates are
batched, we want all updates of like priority that occur within the same
event to receive the same expiration time. Otherwise we get tearing.

We keep track of two separate times: the current "renderer" time and the
current "scheduler" time. The renderer time can be updated whenever; it
only exists to minimize the calls performance.now.

But the scheduler time can only be updated if there's no pending work,
or if we know for certain that we're not in the middle of an event.
2018-06-19 10:34:19 -07:00
..
npm Split ReactNoop into normal and persistent exports (#12793) 2018-05-14 13:57:33 +01:00
src Always batch updates of like priority within the same event (#13071) 2018-06-19 10:34:19 -07:00
index.js Remove vars (#11766) 2017-12-05 13:47:57 +00:00
package.json Remove transitive dependency on fbjs (#13075) 2018-06-19 17:52:37 +01:00
persistent.js Split ReactNoop into normal and persistent exports (#12793) 2018-05-14 13:57:33 +01:00
README.md Add Fiber Debugger (#8033) 2016-10-25 08:36:37 +01:00

react-noop-renderer

This package is the renderer we use for debugging Fiber. It is not intended to be used directly.