-
Notifications
You must be signed in to change notification settings - Fork 4.6k
core-data: use Object.fromEntries instead of reduce when generating entities reducer #36296
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
Conversation
e8c5057 to
2712807
Compare
|
Size Change: -12 B (0%) Total Size: 1.92 MB
ℹ️ View Unchanged
|
|
I think this needs rebasing/conflict resolution, and then can be merged. |
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
2712807 to
986419f
Compare
|
Flaky tests detected in 986419f. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/17153564416
|
Mamaduka
left a comment
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.
Let's merge this. The code looks good and CI checks should've caught anything I missed when testing manually.
A little code quality improvement in the code that generates the
entitiesnested reducer fromentitiesConfig. When creating objects from arrays, useObject.fromEntriesinstead ofreduce( ( memo, ... ) ). Also, I added a comment that explains how the input and output data look like.