Lodash: Refactor away from _.kebabCase() in getCleanTemplatePartSlug
#51906
Conversation
This file contains 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
tyxla
added
[Type] Performance
tyxla
requested review from
Mamaduka,
sgomes,
aristath,
jsnajdr,
swissspidy,
flootr,
chad1008,
ntsekouras and
fabiankaegy
|
Size Change: +185 B (0%) Total Size: 1.44 MB
ℹ️ View Unchanged
|
ntsekouras
approved these changes
Jun 26, 2023
sethrubenstein
pushed a commit
to pewresearch/gutenberg
that referenced
this pull request
Jul 13, 2023
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.
What?
This PR removes Lodash's
_.kebabCase()from thegetCleanTemplatePartSlughelper function.We have a few more usages of
kebabCase()left in the codebase, but we might have to tread carefully, since some of them may have to deal with unicode characters, and I prefer testing those one by one.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-fetchpackage haslodashas a dependency #39495How?
We're replacing the usage with
paramCasefrom thechange-casepackage, which we've already been utilizing for the general use cases. That's fine, since the utility function already claims to support only latin letters.Testing Instructions
/wp-admin/site-editor.php?path=%2FlibraryCustom % template part #$, or try with some unicode characters, like Japanese for examplecustom-template-part.