-
Notifications
You must be signed in to change notification settings - Fork 47k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Context improvements #10334
Merged
Merged
Context improvements #10334
Changes from 5 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
a361a50
Refactored fiber context to fix a nested updates bug
bvaughn e113731
Refactored ReactIncremental-test to use ReactNoop instead of ReactDOM…
bvaughn 97c3de6
Added a to prevent an unnecessary Flow warning
bvaughn 14e3af9
Tidying up comments
bvaughn 101c78c
Fixed typo in test name
bvaughn 252e8f1
Combined conditional branches in ReactFiberContext to be more efficient
bvaughn File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -234,14 +234,22 @@ exports.pushContextProvider = function(workInProgress: Fiber): boolean { | |
emptyObject; | ||
|
||
// Remember the parent context so we can merge with it later. | ||
// Inherit the parent's did-perform-work value to avoid inadvertantly blocking updates. | ||
previousContext = contextStackCursor.current; | ||
push(contextStackCursor, memoizedMergedChildContext, workInProgress); | ||
push(didPerformWorkStackCursor, false, workInProgress); | ||
push( | ||
didPerformWorkStackCursor, | ||
didPerformWorkStackCursor.current, | ||
workInProgress, | ||
); | ||
|
||
return true; | ||
}; | ||
|
||
exports.invalidateContextProvider = function(workInProgress: Fiber): void { | ||
exports.invalidateContextProvider = function( | ||
workInProgress: Fiber, | ||
didChange: boolean, | ||
): void { | ||
const instance = workInProgress.stateNode; | ||
invariant( | ||
instance, | ||
|
@@ -250,20 +258,23 @@ exports.invalidateContextProvider = function(workInProgress: Fiber): void { | |
); | ||
|
||
// Merge parent and own context. | ||
const mergedContext = processChildContext( | ||
workInProgress, | ||
previousContext, | ||
true, | ||
); | ||
instance.__reactInternalMemoizedMergedChildContext = mergedContext; | ||
// Skip this if we're not updating due to sCU. | ||
// This avoids unnecessarily recomputing memoized values. | ||
let mergedContext; | ||
if (didChange) { | ||
mergedContext = processChildContext(workInProgress, previousContext, true); | ||
instance.__reactInternalMemoizedMergedChildContext = mergedContext; | ||
} | ||
|
||
// Replace the old (or empty) context with the new one. | ||
// It is important to unwind the context in the reverse order. | ||
pop(didPerformWorkStackCursor, workInProgress); | ||
pop(contextStackCursor, workInProgress); | ||
// Now push the new context and mark that it has changed. | ||
push(contextStackCursor, mergedContext, workInProgress); | ||
push(didPerformWorkStackCursor, true, workInProgress); | ||
if (didChange) { | ||
pop(contextStackCursor, workInProgress); | ||
// $FlowFixMe - We know that this is always an object when didChange is true. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Suggested refactor: if (didChange) {
const mergedContext = processChildContext(workInProgress, previousContext, true);
instance.__reactInternalMemoizedMergedChildContext = mergedContext;
pop(didPerformWorkStackCursor, workInProgress);
pop(contextStackCursor, workInProgress);
push(contextStackCursor, mergedContext, workInProgress);
} else {
pop(didPerformWorkStackCursor, workInProgress);
} One fewer branch and prevents Flow from complaining. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I like this suggestion. Check out the most recent commit. It cool? |
||
push(contextStackCursor, mergedContext, workInProgress); | ||
} | ||
push(didPerformWorkStackCursor, didChange, workInProgress); | ||
}; | ||
|
||
exports.resetContext = function(): void { | ||
|
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is also a sCU on functional components but since that's a new thing I guess we could ignore that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But as long as it's in the codebase, I think we should keep the implementations in sync.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That means that we have to push/pop every functional component though, right? That seems like we're severely punishing perf of functional components for this edge case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess I misunderstood @bvaughn's original description of this change as a bugfix, or improvement to a more correct behavior. Subsequent comments suggest otherwise.
Now that I think about it, this only affects context providers, right? So I guess functional components aren't affected?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The difference is whether functional components can terminate rendering. They can't with this PR if the context provider rerendered above them. Basically sCU on a functional component becomes useless in many cases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually I'm not sure what happens... They don't get priority and pending props, so maybe things don't rerender?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change shouldn't be relevant for functional components, since it's specific to context-providers. Functional components can only consume context, since there's no underlying instance. Right?