Fix filter parameter shadowing on locateIn #5062
Closed
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.
The signature of
locateIn
includes afilter
that is not used in the current definition of the function. This is causing some issues during the bundling onmaster
for me. This is whatlocateIn
and `locate ends up looking like:Note that the
filter
argument inlocateVisible
is removed, probably because the bundler can tell that the argument goes unused. ThenlocateIn
callsfilter
from its argument list, which shadows the originalArr.filter
, causing afilter is not a function
error.This is what the same block looks like from this branch: