Consideration for Alternate Array Handling about merge-options HOT 3 CLOSED

Mhm, doesn't concatArrays work for you?

const result = mergeOptions.call({concatArrays: true}, {}, {a:[3]}, {a:[1,2]});
// { a: [3, 1, 2] }

That could support multiple different methods (which could even be user-extendible), with the default being the current behavior of right-most replacement as an object value.

Can you elaborate this and give some examples? Maybe you are on the track of something.

from merge-options.

@schnittstabil man, I completely missed that option, thanks for pointing it out.

So in scenarios where options need to be passed to a method that typically operates on all ...args, it's typically easier on users and sanity checking to provide a factory method which accepts only an options argument and returns an instance of the method which is scope-configured according to the options passed to the factory. In that way, mergeOptions.set({ concatArray: true }) would return an instance of mergeOptions which could then be called such like mergeOptions(obj1, obj2, ...) without having to remember to have the first object be an options object. It also provides reuse of that configured instance without having to manually wrap mergeOptions.

from merge-options.

If I understand you correctly, you can already accomplish that via Function.prototype.bind():

const mergeOptions = require('merge-options');

const merge = mergeOptions.bind({concatArrays: true})
merge({}, {a:[3]}, {a:[1,2]});
// { a: [ 3, 1, 2 ] }

from merge-options.