-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Serialize the map objects properly in the Redux dev tools #46282
Conversation
Size Change: +34 B (0%) Total Size: 1.33 MB
ℹ️ View Unchanged
|
I wonder if this is something to do for There might be some optimization around that too, although it might still be necessary to create a That may be a problem with |
We do create Maps on each change, but it's still more performant than creating and spreading objects on each change.
I didn't see any of that in any of the refactored reducers. |
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.
Looks good, thanks!
Are we already using "Set" objects in reducers, couldn't find any? |
You're right, there are a couple of cases in actions/resolvers, but not as many as I thought (should've checked beforehand). Not worth worrying about then. |
What?
Ref: #46146 (comment)
After the recent refactoring of the block editor store to use maps instead of plain objects, the redux dev tools stopped showing the state properly. This PR transforms back the "maps" into "objects" in the Redux dev tools to show the updates properly there.
Testing Instructions