set-value

set-value copied to clipboard

Dont delete number keys

1

This fixes #35 by checking if the target is an object instead of explicitly an array.

snowbldr

Array support causing unexpected value manipulated

4

Hi, there Since our team recently upgraded set-value from v3 to v4, we found there's a severe problem dealing with numeric path. before v4 paths are treated as properties, so...

jasperjn

Node sure how out-of-date your benchmarking package is, but it doesn't seem to want to run, something about the file globbing just not working ```sh C:\Git\set-value\benchmark>node . Error: ENOENT: no...

seanblonien

bug https://huntr.dev/bounties/db58816d-adf9-4847-ab8e-3fdb035aca1f

ranjit-git

Some test cases you may want to add. https://replit.com/@trajano/lodash#index.js ``` const _ = require('lodash'); const set = require('set-value'); const spec = { a: "foo", b: { x: 12, y: 11...

trajano

I'm missing an option to insert value into Array instead of overwriting the existing value. Similar to the `merge` option that currently exists for Objects. Something like: ``` obj =...

havardthom

Fixes https://github.com/jonschlinkert/set-value/issues/36

havardthom

CHANGELOG for v2 → v3 → v4 (list of breaking changes)

1

I see a number of warnings from `yarn audit` because some project dependencies still rely on `set-value` v2 and v3. While it’s technically possible to force-install v4 via `package.json` →...

kachkaev

I have a use case where I need to set a value explicitly to undefined. In the current state, it's not possible to use this function to accomplish my goals....

snowbldr

upgrade 2.0.1 to 4.0.1 to fix the vulnerability.

5

This is my tree structure of set-value :  i want to upgrade it to 4.0.1 i tried to update set-value with latest and its parent packages but issue is...

BhagyashreeYogeshChaudhari