fix(compat/merge): use isArrayLikeObject to match lodash merge behavior #1542
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.
PR Description
Problem
es-toolkit/compat's merge() produces different results than Lodash when a nested object property is replaced by an array from the source.
Root Cause
In mergeWith.ts, when source is an array, the code treated all objects the same - copying every property to the new array:
Lodash (_baseMergeDeep.js lines 53-70) distinguishes three cases
using isArrayLikeObject:
Solution
Use isArrayLikeObject to match Lodash's logic:
Test
Added test cases in merge.spec.ts and mergeWith.spec.ts: