_.pick is incorrectly simplified, Lodash accepts a path

[alejandroiglesias]

The Lodash version of pick accepts a path, thus this is perfectly doable in Lodash:

var object = { 'a': 1, 'b': '2', 'c': { 'd' : 3 } };

// Underscore/Lodash
var result = _.pick(object, ['a', 'c.d']);
console.log(result)
// output: {a: 1, c: {d: 3}}

But there's no equivalent in ES6.

By the way, _.pickBy is displayed incorrectly since it's missing the second parameter which is a function to evaluate if prop will be picked.

[cht8687]

👍 thanks for pointing it out. As stated in the very beginning of the doc:

Please note that the examples used below are just showing you the native alternative of performing certain tasks. For some functions, Lodash provides you more options than native built-ins. This list is not a 1:1 comparison.

we can fix the example though.

[dietergeerts]

👍 thanks for pointing it out. As stated in the very beginning of the doc:

Please note that the examples used below are just showing you the native alternative of performing certain tasks. For some functions, Lodash provides you more options than native built-ins. This list is not a 1:1 comparison.

we can fix the example though.

Please update the example and clearly state what Lodash does extra, so that devs see that using Lodash still is very valuable for these things. Devs don't seem to read these side notes these days, as I have enough explaining to do why using Lodash is still a good thing, just because they see things like this, and then start to think that Lodash should be deprecated because you can do everything natively! The native way isn't always readable, and readability > not using libraries.