Sebastian Markbage bebc568ceb Use Singleton LifeCycle State ...

All entry points are for reconciliation are within batching strategies.

Since we don't have any batching strategies with synchronous updates,
there can't be more than one life-cycle method on the stack at any given
time.

Therefore, it's safe to move the composite life cycle flag to a singleton.
This saves us some memory management.

I think that we can get rid of these life cycle states completely in the
future.

2015-01-27 01:19:31 -08:00

..

addons

Batch updates in initial render

2015-01-27 01:00:59 -08:00

browser

Batch updates in initial render

2015-01-27 01:00:59 -08:00

classic

Use Singleton LifeCycle State

2015-01-27 01:19:31 -08:00

core

Use Singleton LifeCycle State

2015-01-27 01:19:31 -08:00

event

[lint] Fix majority of issues eslint found

2015-01-13 15:26:33 -08:00

modern

Extract setState, setProps etc into ReactUpdateQueue

2015-01-27 00:55:25 -08:00

stubs

codemod "use strict" to 'use strict' for better linting

2015-01-13 15:26:32 -08:00

test

Add Meta Matchers for Testing Tests

2015-01-26 15:50:57 -08:00

utils

Update warning calls to use %s #2870

2015-01-26 21:39:43 -06:00

vendor

Move propType validation to element instead of class.

2015-01-26 17:16:49 -08:00

vendor_deprecated

Add 'use strict' to statisfy linter rules

2014-11-01 07:05:46 +02:00

.eslintrc

Use eslint

2015-01-13 14:01:34 -08:00

.jshintrc

Remove obsolete jshint options

2014-10-26 12:18:24 +02:00

package.json

Initial public release

2013-05-29 12:54:02 -07:00