Commit Graph

1921 Commits

Author SHA1 Message Date
Ben Alpert 4eb889b72e Revert "Removed setProps and replaceProps (both previously deprecated)"
This reverts commit 721fe73541. We'll keep these with a warning for one more release.
2015-07-03 10:46:35 +02:00
Ben Alpert 33d5201a94 Finish addons packaging
- Add missing object-assign dependency
- Add batchedUpdates to ReactDOMClient, rename the two addons to `unstable_`
- Delete react/addons/* (leaving react/addons with a slightly updated warning)
- Add README.md, LICENSE, PATENTS to each addons package
2015-07-02 23:33:16 +02:00
Ben Alpert 0eaa0a6ff7 Fix jest tests 2015-07-02 22:54:22 +02:00
Ben Alpert 07107ca936 Merge pull request #4184 from zpao/move-from-addons
Move renderSubtreeIntoContainer into ReactDOMClient
2015-07-02 22:53:47 +02:00
Kamron Batman 72b432df03 Fixed header comment spacing.
Fixed header comment spacing in the header for ReactComponentWithPureRenderMixin.
2015-07-02 09:36:52 -07:00
Jim 2baf4bf4e8 Merge pull request #4268 from jimfb/remove-setprops
Removed setProps and replaceProps (both previously deprecated)
2015-07-02 04:47:18 -07:00
Jim 6a92179d6f Merge pull request #4221 from jimfb/ryans-context-bug
updateComponent should update the context iff it has changed
2015-07-02 04:45:41 -07:00
Jim 4a465fbd9a Make events propagate through shadow DOMs. 2015-07-02 04:32:22 -07:00
Jim 721fe73541 Removed setProps and replaceProps (both previously deprecated) 2015-07-02 04:00:58 -07:00
Jim 8953033454 Merge pull request #4259 from janraasch/patch-1
Add IE-only security attr to HTMLDOMPropertyConfig
2015-07-01 18:15:39 -07:00
Jan Raasch b089b427ab Add IE-only security attr to HTMLDOMPropertyConfig
See https://msdn.microsoft.com/en-us/library/ms534622(v=vs.85).aspx for an in-depth specification.

This fixes #4169.
2015-07-01 19:47:48 +02:00
Sebastian Markbåge 8f9643485d Merge pull request #4162 from sebmarkbage/updator
Inject the update queue into classes
2015-07-01 17:46:05 +02:00
Ben Alpert c22153e25a Fail tests on any un-spied warnings
Fixes #3890.
2015-06-29 07:57:35 -07:00
Jim 289962f6f8 Don't bail out of reconsiliation if context changes. 2015-06-25 00:58:05 -07:00
li.li 63d0471580 Remove warnings in tests
For #3890.

Squashed merge, closes #3925.
2015-06-24 22:01:36 -07:00
Ben Alpert 8f217c8a4b Merge pull request #4215 from spicyj/prod-props
Set this.props on elements in prod mode
2015-06-24 16:38:14 -07:00
Ben Alpert 9ba28f317b Merge pull request #4200 from spicyj/ten-thousand
Allow deeper trees
2015-06-24 16:33:30 -07:00
Ben Alpert 9c8c11dd07 Set this.props on elements in prod mode
Oops. Introduced in https://github.com/facebook/react/pull/4172.
2015-06-24 16:26:40 -07:00
Jim 4431c90fa4 Merge pull request #4208 from battaile/master
Minor cleanup of ReactES6Class-test output by expecting the warning
2015-06-24 08:18:44 -07:00
Battaile Fauber 41df3ce421 Check for warning when testing to see if error is thrown when render not defined 2015-06-24 08:03:36 -04:00
yiminghe ee831d7550 optimize spec 2015-06-24 17:13:41 +08:00
yiminghe 47e9cfb975 fix change event type 2015-06-24 17:06:35 +08:00
JD Isaacks d944d3f941 Prevent creating invalid closing tags
fixes #2756
2015-06-23 17:58:52 -04:00
Ben Alpert fdaefc1103 Allow deeper trees
No reason to limit at 100. I can't imagine a reasonable tree with depth over 10,000 but that should still be small enough to "catch infinite loops" quickly.
2015-06-23 14:07:05 -07:00
Ben Alpert c5fb3ff987 Merge pull request #4139 from spicyj/dom-refs
DOM components as refs
2015-06-22 16:58:01 -07:00
Ben Alpert d810079101 Remove constructAndRenderComponent
These were never part of the public API and shouldn't have been part of the React object. Now they're not.
2015-06-22 16:55:19 -07:00
Ben Alpert eefda9377c Add legacy methods to DOM components for compatibility 2015-06-22 16:51:21 -07:00
Ben Alpert ffd527f593 DOM components as refs
Still missing: .props/.getDOMNode warnings.
2015-06-22 16:51:21 -07:00
Ben Alpert 643651b8e5 Wrap all top-level components for consistency 2015-06-22 16:51:04 -07:00
Sebastian Markbåge 9d2c9b5864 Merge pull request #4196 from oluckyman/componentDidUnmount-warning
Show warning when componentDidUnmount is defined
2015-06-22 16:48:27 -07:00
oluckyman 2568933ca3 Update warn message and move it to the error-catching block 2015-06-22 23:52:37 +02:00
Jim 859b7957b7 Merge pull request #4190 from dantman/fix-%s-module
Don't try building a %s module.
2015-06-22 14:45:19 -07:00
Ben Alpert 7e0a544ae3 Merge pull request #4164 from spicyj/jest-wc
Fix exceptions when running `grunt test --debug`
2015-06-22 14:22:41 -07:00
oluckyman db40beafbe Show warning when componentDidUnmount is defined
Fixes #4194
2015-06-22 21:09:33 +02:00
Daniel Friesen 357ed8ebd7 Add a comment about why the string is split up. For future readers of this file. 2015-06-22 12:04:29 -07:00
Daniel Friesen c8d606196d Don't try building a %s module.
React's build tools are reading the `require("react")` and `react("%s")` inside the warning string and thinking they are actual requires.
2015-06-21 21:14:04 -07:00
Paul O’Shannessy bbadc15ac1 Move renderSubtreeIntoContainer into ReactDOMClient 2015-06-20 18:08:33 -07:00
Ben Alpert 64b5f043dd Merge pull request #4170 from johanneslumpe/patch-1
Guard against a null node
2015-06-20 16:42:23 -07:00
Jim ede27d2e86 Merge pull request #4172 from jimfb/freeze-props
Freeze ReactElement.props in dev mode
2015-06-19 14:13:17 -07:00
Johannes Lumpe b16f9d42b1 Guard against a null node
This could fix #2619
2015-06-19 11:21:22 +03:00
Sebastian Markbage c1330dcfcd Unit tests for unmounted setState and isMounted 2015-06-18 22:55:52 -07:00
Jim 95373ce769 Freeze ReactElement.props in dev mode 2015-06-18 14:49:06 -07:00
Sebastian Markbage 8659223939 Lint fixes 2015-06-18 14:12:21 -07:00
Sebastian Markbage dddebd1344 Use hack to support isMounted without stateful module
This hack allow us to get rid of the stateful module ReactLifeCycle since
we can infer the value of isMounted even without it. This gets rid of
the try/catch which is deopting all mountComponent calls.

As a next step we could deprecate isMounted completely and avoid stateful
APIs. Since it can be easily simulated if you truly need it.
2015-06-18 14:10:12 -07:00
Sebastian Markbage 140af9b985 Allow callbacks to be enqueued during componentWillMount
Since I fixed the server-side rendering it is now possible to trigger these
callbacks on the client alone. They will still be queued up on the server
but they are never executed.
2015-06-18 13:35:39 -07:00
Sebastian Markbage e737acb472 Let updates be enqueued during render
This allows updates to be enqueued during render. setState in
componentWillMount will still be collected as part of the first pass so
if nothing else get added as pending, they won't trigger a second rerender.

This allow us to get rid of one more stateful special case.
2015-06-18 13:35:39 -07:00
Sebastian Markbage 40b7c19a89 Use a custom batching strategy for server rendering
This simply ignores any enqueued actions. This means that we don't have to have special logic for componentWillMount. It is just that those updates are never enqueued.
2015-06-18 13:34:30 -07:00
Sebastian Markbage 3af73834d9 Remove currentlyUnmountingComponent
This was used for any invariant that was subsequently removed. It turns
out that this is completely unnecessary now. Any setState calls will
enqueue and update and the component added to the update queue. However,
since the pending fields are reset after componentWillUnmount, any update
will still be ignored.
2015-06-18 12:36:50 -07:00
Sebastian Markbage 7443f63ae9 Remove an unnecessary warning
It was impossible to get here because if you enqueue something

Also ensure that they're only used in DEV because we will be reading
state that is DEV only here.
2015-06-18 12:36:45 -07:00
Sebastian Markbage c4cafcecd9 Move current owner to isomorphic
This should only be used for tracking string refs. For that purpose, we
need a single central stateful module that is coupled to createElement.
Which is why it needs to live in isomorphic.

Eventually this will go away completely.
2015-06-18 09:05:35 -07:00