Brian Vaughn 1b868cbd71 Don't warn about class component usage of getInitialState if state is also set ...

We warn about getInitialState() usage in class components because users may have accidentally used it instead of state. If they have also specified state though then we should skip this warning.

Context: https://twitter.com/soprano/status/810003963286163456

2016-12-17 11:16:27 -08:00

..

babel

Make React.__spread warn

2016-04-07 17:30:23 -07:00

bench

Fix benchmarks (#7704)

2016-09-12 21:58:00 +03:00

circleci

Disable coverage on PRs on Circle (#8569)

2016-12-13 14:27:25 -08:00

error-codes

Fix error codes (#7999)

2016-11-08 20:20:46 +00:00

facts-tracker

Probably fix facts tracker

2016-12-07 16:04:47 -08:00

fiber

Don't warn about class component usage of getInitialState if state is also set

2016-12-17 11:16:27 -08:00

git

Remove leftover env variable logic in pre-commit hook

2015-09-01 14:35:47 -07:00

jest

Build infra for tracking dev-specific failures (#8228)

2016-11-13 14:00:07 -08:00

perf-counters

Year-agnostic copyright message, like React Native uses, to prevent the need for yearly changes.

2015-12-29 20:20:32 +01:00

authors

AUTHORS

2013-09-09 23:42:54 -07:00