Dayong Lee
Dayong Lee
Ah, this was put on hold per previous discussion with maintainers. Let me sync up and update.
After thinking about it more, I think this needs to be addressed in the next major update, so I'll discuss internally about the timing of the next major release. Sorry...
Since es-toolkit/compat follows lodash's types and behavior, we're not making additional improvements to it separately. However, allowing both to be disabled in the original functions does seem meaningless. There's obviously...
After thinking about it more, since this is a breaking change, it seems difficult to apply immediately. I'll make sure to include it in the next major update.
This is a really great suggestion! I especially love that we can write while looking at the documentation. Would you be able to work on this even lightly, even if...
In fact, lodash also has inconsistencies in certain situations: ```ts import _ from 'lodash'; console.log(_.merge({ x: { a: 2 } }, { x: ['1'] }).x); // Current: ['1'] // Expected:...
After more thought, I still believe preserving the target structure is the correct behavior. Here's why: **1. Consistency with `Object.assign`:** ```javascript Object.assign({ a: 1 }, { b: 2 }) //...
Thanks for bringing this up! 🙏 I've updated the implementation based on your feedback — Object.assign should now work recursively as expected. Really appreciate the report!
https://github.com/toss/es-toolkit/pull/1553
@AlexHartford Could you share the reproducible project repository, if available? I need it for debugging purposes.