-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[HOLD for payment 2023-10-30] Optimize React Context usages in New Expensify #28177
Comments
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.88-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-10-30. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
all done here |
Coming from: https://expensify.slack.com/archives/C05LX9D6E07/p1695377829998599
Problem:
Poorly implemented React Context will lead to unnecessary re-renders of Context.Consumers.
Solution:
Making sure that each time React Context is used, the value passed to Context.Provider will be properly memoized. Apart from fixing problem in existing files it would be nice to share the knowledge to developers (and reviewers) to pay attention to this problem.
Go through this list and optimize these context usages:
The text was updated successfully, but these errors were encountered: