invokeMap in fp strange behavior

[JesterXL]

The 2nd example for invokeMap fp don't seem to work, but they work with regular lodash. Using v4.17.4 in Node 10.1.0 and tested in Chrome 67.0.3396.99 on Stackblitz. I'm having various challenges getting it to pass values to functions, so am wondering if this is related?

Regular Lodash:

// works
_.invokeMap([[5, 1, 7], [3, 2, 1]], 'sort')
// [[1, 5, 7], [1, 2, 3]]

// works
_.invokeMap([123, 456], String.prototype.split, '')
// [[1, 5, 7], [1, 2, 3]]

FP Lodash:

// works
invokeMap('sort', [[5, 1, 7], [3, 2, 1]])
// [[1, 5, 7], [1, 2, 3]]

// fails
log(invokeMap([String.prototype.split, ''], [123, 456]))
// [undefined, undefined]

[JesterXL]

Just checked, and it seems invoke has the same issue. I'm referring to these unofficial docs: https://gist.github.com/jfmengels/6b973b69c491375117dc

[jdalton]

Hi @JesterXL!

The fp invokeMap method variant has a fixed arity of 2 (so no args param). We don't currently provide an invokeMapArgs form, however you can use convert to reconfigure it.

[JesterXL]

Ah, makes total sense, ok cool, thanks!

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.