Support sharing context objects between concurrent renderers #12779
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
acdlite
changed the title
acdlite
changed the title
|
React: size: 🔺+0.5%, gzip: 🔺+0.2% ReactDOM: size: 🔺+0.4%, gzip: 🔺+0.6% Details of bundled changes.Comparing: 6565795...82255ac react
react-dom
react-art
react-test-renderer
react-reconciler
react-native-renderer
Generated by 🚫 dangerJS |
sebmarkbage
reviewed
May 11, 2018
| @@ -11,6 +11,7 @@ | |||
|
|
|||
| let React = require('react'); | |||
| let ReactDOM = require('react-dom'); | |||
| let ReactART = require('react-art'); | |||
sebmarkbage
approved these changes
May 11, 2018
sebmarkbage
reviewed
May 11, 2018
packages/react/src/ReactContext.js
Outdated
| _changedBits: 0, | ||
| _changedBits_secondary: 0, |
There was a problem hiding this comment.
_changedBits2? every byte counts.
|
What if I want three? |
acdlite
force-pushed
the
support-concurrent-primary-and-secondary-renderers
branch
from
a211b39
to
2537883
Compare
As a workaround to support multiple concurrent renderers, we categorize some renderers as primary and others as secondary. We only expect there to be two concurrent renderers at most: React Native (primary) and Fabric (secondary); React DOM (primary) and React ART (secondary). Secondary renderers store their context values on separate fields.
Only warn for two concurrent primary or two concurrent secondary renderers.
#EveryBitCounts
acdlite
force-pushed
the
support-concurrent-primary-and-secondary-renderers
branch
from
2537883
to
82255ac
Compare
|
@sophiebits Too bad! :P If we decide later we want to support this in the general case, what we'd do is have each renderer expose a function to reset its stack upon interruption. Kinda slow, but that's effectively what would happen if everything shared the same renderer (i.e. that's what happens when one root interrupts another root). |
gaearon
reviewed
May 15, 2018
| warning( | ||
| context._currentRenderer === null || | ||
| context._currentRenderer === rendererSigil, | ||
| 'Detected multiple renderers concurrently rendering the ' + |
There was a problem hiding this comment.
I'm bumping into this with test renderer when the context object is reused, but resetModules() is called between tests. Seems confusing.
bors bot
added a commit
to mythmon/corsica-tree-status
that referenced
this pull request
May 24, 2018
20: Update react monorepo to v16.4.0 r=renovate[bot] a=renovate[bot] This Pull Request renovates the package group "react monorepo". - [react-dom](https://github.com/facebook/react) (`dependencies`): from `16.3.2` to `16.4.0` - [react](https://github.com/facebook/react) (`dependencies`): from `16.3.2` to `16.4.0` # Release Notes <details> <summary>facebook/react</summary> ### [`v16.4.0`](https://github.com/facebook/react/blob/master/CHANGELOG.md#​1640-May-23-2018) [Compare Source](facebook/react@8e5f12c...v16.4.0) ##### React * Add a new [experimental](`reactjs/rfcs#51) `React.unstable_Profiler` component for measuring performance. ([@​bvaughn] in [#​12745](`facebook/react#12745)) ##### React DOM * Add support for the Pointer Events specification. ([@​philipp-spiess] in [#​12507](`facebook/react#12507)) * Properly call `getDerivedStateFromProps()` regardless of the reason for re-rendering. ([@​acdlite] in [#​12600](`facebook/react#12600) and [#​12802](`facebook/react#12802)) * Fix a bug that prevented context propagation in some cases. ([@​gaearon] in [#​12708](`facebook/react#12708)) * Fix re-rendering of components using `forwardRef()` on a deeper `setState()`. ([@​gaearon] in [#​12690](`facebook/react#12690)) * Fix some attributes incorrectly getting removed from custom element nodes. ([@​airamrguez] in [#​12702](`facebook/react#12702)) * Fix context providers to not bail out on children if there's a legacy context provider above. ([@​gaearon] in [#​12586](`facebook/react#12586)) * Add the ability to specify `propTypes` on a context provider component. ([@​nicolevy] in [#​12658](`facebook/react#12658)) * Fix a false positive warning when using `react-lifecycles-compat` in `<StrictMode>`. ([@​bvaughn] in [#​12644](`facebook/react#12644)) * Warn when the `forwardRef()` render function has `propTypes` or `defaultProps`. ([@​bvaughn] in [#​12644](`facebook/react#12644)) * Improve how `forwardRef()` and context consumers are displayed in the component stack. ([@​sophiebits] in [#​12777](`facebook/react#12777)) * Change internal event names. This can break third-party packages that rely on React internals in unsupported ways. ([@​philipp-spiess] in [#​12629](`facebook/react#12629)) ##### React Test Renderer * Fix the `getDerivedStateFromProps()` support to match the new React DOM behavior. ([@​koba04] in [#​12676](`facebook/react#12676)) * Fix a `testInstance.parent` crash when the parent is a fragment or another special node. ([@​gaearon] in [#​12813](`facebook/react#12813)) * `forwardRef()` components are now discoverable by the test renderer traversal methods. ([@​gaearon] in [#​12725](`facebook/react#12725)) * Shallow renderer now ignores `setState()` updaters that return `null` or `undefined`. ([@​koba04] in [#​12756](`facebook/react#12756)) ##### React ART * Fix reading context provided from the tree managed by React DOM. ([@​acdlite] in [#​12779](`facebook/react#12779)) ##### React Call Return (Experimental) * This experiment was deleted because it was affecting the bundle size and the API wasn't good enough. It's likely to come back in the future in some other form. ([@​gaearon] in [#​12820](`facebook/react#12820)) ##### React Reconciler (Experimental) * The [new host config shape](https://github.com/facebook/react/blob/c601f7a64640290af85c9f0e33c78480656b46bc/packages/react-noop-renderer/src/createReactNoop.js#L82-L285) is flat and doesn't use nested objects. ([@​gaearon] in [#​12792](`facebook/react#12792)) --- </details> --- This PR has been generated by [Renovate Bot](https://renovatebot.com). Co-authored-by: Renovate Bot <bot@renovateapp.com>
bors bot
added a commit
to mozilla/delivery-console
that referenced
this pull request
May 24, 2018
164: Update react monorepo to v16.4.0 r=rehandalal a=renovate[bot] This Pull Request renovates the package group "react monorepo". - [react-dom](https://github.com/facebook/react) (`dependencies`): from `16.3.2` to `16.4.0` - [react](https://github.com/facebook/react) (`dependencies`): from `16.3.2` to `16.4.0` # Release Notes <details> <summary>facebook/react</summary> ### [`v16.4.0`](https://github.com/facebook/react/blob/master/CHANGELOG.md#​1640-May-23-2018) [Compare Source](facebook/react@8e5f12c...v16.4.0) ##### React * Add a new [experimental](`reactjs/rfcs#51) `React.unstable_Profiler` component for measuring performance. ([@​bvaughn] in [#​12745](`facebook/react#12745)) ##### React DOM * Add support for the Pointer Events specification. ([@​philipp-spiess] in [#​12507](`facebook/react#12507)) * Properly call `getDerivedStateFromProps()` regardless of the reason for re-rendering. ([@​acdlite] in [#​12600](`facebook/react#12600) and [#​12802](`facebook/react#12802)) * Fix a bug that prevented context propagation in some cases. ([@​gaearon] in [#​12708](`facebook/react#12708)) * Fix re-rendering of components using `forwardRef()` on a deeper `setState()`. ([@​gaearon] in [#​12690](`facebook/react#12690)) * Fix some attributes incorrectly getting removed from custom element nodes. ([@​airamrguez] in [#​12702](`facebook/react#12702)) * Fix context providers to not bail out on children if there's a legacy context provider above. ([@​gaearon] in [#​12586](`facebook/react#12586)) * Add the ability to specify `propTypes` on a context provider component. ([@​nicolevy] in [#​12658](`facebook/react#12658)) * Fix a false positive warning when using `react-lifecycles-compat` in `<StrictMode>`. ([@​bvaughn] in [#​12644](`facebook/react#12644)) * Warn when the `forwardRef()` render function has `propTypes` or `defaultProps`. ([@​bvaughn] in [#​12644](`facebook/react#12644)) * Improve how `forwardRef()` and context consumers are displayed in the component stack. ([@​sophiebits] in [#​12777](`facebook/react#12777)) * Change internal event names. This can break third-party packages that rely on React internals in unsupported ways. ([@​philipp-spiess] in [#​12629](`facebook/react#12629)) ##### React Test Renderer * Fix the `getDerivedStateFromProps()` support to match the new React DOM behavior. ([@​koba04] in [#​12676](`facebook/react#12676)) * Fix a `testInstance.parent` crash when the parent is a fragment or another special node. ([@​gaearon] in [#​12813](`facebook/react#12813)) * `forwardRef()` components are now discoverable by the test renderer traversal methods. ([@​gaearon] in [#​12725](`facebook/react#12725)) * Shallow renderer now ignores `setState()` updaters that return `null` or `undefined`. ([@​koba04] in [#​12756](`facebook/react#12756)) ##### React ART * Fix reading context provided from the tree managed by React DOM. ([@​acdlite] in [#​12779](`facebook/react#12779)) ##### React Call Return (Experimental) * This experiment was deleted because it was affecting the bundle size and the API wasn't good enough. It's likely to come back in the future in some other form. ([@​gaearon] in [#​12820](`facebook/react#12820)) ##### React Reconciler (Experimental) * The [new host config shape](https://github.com/facebook/react/blob/c601f7a64640290af85c9f0e33c78480656b46bc/packages/react-noop-renderer/src/createReactNoop.js#L82-L285) is flat and doesn't use nested objects. ([@​gaearon] in [#​12792](`facebook/react#12792)) --- </details> --- This PR has been generated by [Renovate Bot](https://renovatebot.com). Co-authored-by: Renovate Bot <bot@renovateapp.com>
This was referenced May 24, 2018
This was referenced May 28, 2018
This was referenced Jun 4, 2018
This was referenced Jun 11, 2018
This was referenced Nov 1, 2018
NMinhNguyen
referenced
this pull request
in enzymejs/react-shallow-renderer
Jan 29, 2020
* Support concurrent primary and secondary renderers. As a workaround to support multiple concurrent renderers, we categorize some renderers as primary and others as secondary. We only expect there to be two concurrent renderers at most: React Native (primary) and Fabric (secondary); React DOM (primary) and React ART (secondary). Secondary renderers store their context values on separate fields. * Add back concurrent renderer warning Only warn for two concurrent primary or two concurrent secondary renderers. * Change "_secondary" suffix to "2" #EveryBitCounts
This was referenced Jul 14, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As a workaround to support multiple concurrent renderers, we categorize some renderers as primary and others as secondary. We only expect there to be two concurrent renderers at most: React Native (primary) and Fabric (secondary); React DOM (primary) and React ART (secondary). Secondary renderers store their context values on separate fields.