-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Lodash: Remove _.pickBy()
from template deletion
#46975
Conversation
return id !== template.slug; | ||
} | ||
const newAvailableTemplates = Object.fromEntries( | ||
Object.entries( settings.availableTemplates ?? {} ).filter( |
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.
settings.availableTemplates
could potentially be nullish, therefore we're adding a fallback to keep the original _.pickBy()
behavior of always returning an object.
Size Change: +32 B (0%) Total Size: 1.32 MB
ℹ️ View Unchanged
|
Flaky tests detected in 1f5a782. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/3874049306
|
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.
LGTM 👍
What?
This PR removes Lodash's
_.pickBy()
from the post editor template deletion component. There is just a single usage in that component and conversion is pretty straightforward.Why?
Lodash is known to unnecessarily inflate the bundle size of packages, and in most cases, it can be replaced with native language functionality. See these for more information and rationale:
@wordpress/api-fetch
package haslodash
as a dependency #39495How?
We're using
Object.fromEntries( Object.entries() )
withArray.prototype.filter()
instead of_.pickBy()
.Testing Instructions