Components: Refactor Autocomplete away from _.deburr()#42266
Merged
Conversation
tyxla
added
[Feature] Inserter
tyxla
requested review from
aristath,
chad1008,
ciampo,
fabiankaegy,
gziolo,
mirka,
ntsekouras and
swissspidy
|
Size Change: -2 B (0%) Total Size: 1.25 MB
ℹ️ View Unchanged
|
tyxla
force-pushed
the
refactor/deburr-autocomplate
branch
from
cef1952 to
9e8c821
Compare
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
2 participants
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 the
_.deburr()usage from theAutocompletecomponent.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
_.deburr()with compactremove-accentslibrary that we've already been using for that purpose.Testing Instructions
Follow the instructions in #10489 or #10770 and verify it still works as described there.