fix(makeStyles): Fix object literal outside useMemo causing styles to change on every render - #3844
Merged
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## next #3844 +/- ##
==========================================
- Coverage 79.71% 79.68% -0.04%
==========================================
Files 87 87
Lines 1844 1846 +2
Branches 821 803 -18
==========================================
+ Hits 1470 1471 +1
- Misses 369 370 +1
Partials 5 5 ☔ View full report in Codecov by Sentry. |
arpitBhalla
approved these changes
Feb 4, 2024
15 tasks
This file contains hidden or 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
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.
Motivation
We found that the return value of
makeStyleswas changing on every render, which impacts performance, and makes it impossible to use it as a dependency ofuseMemoetc. without getting a "maximum update depth exceeded" error.This change resolves this issue by ensuring the empty object literal used when no props are given is created inside the
useMemo.Type of change
How Has This Been Tested?
exampleappChecklist
yarn docs-build-apiAdditional context