`dset` throws when encountering `null` in object
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 783
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
This test currently fails:
```js
objects(`should ${verb} null values`, () => {
let { input } = prepare({ hello: null });
dset(input, ['hello', 'a'], 123);
assert.equal(input, {
hello: { a: 123 },
});
});
```
with:
```
FAIL objects "should overwrite null values"
Cannot set properties of null (setting 'a')
```
lodash.set correctly overwrites `null`.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the failing objects test shown in the issue and the dset entry point; run the test to reproduce the null assignment failure. Update the behavior so a null value is replaced with an object containing the requested nested value, then confirm the test passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100