casts `undefined` to empty object

[c-vetter]

When I run omitDeep({ x: undefined }, 'y')
I expect to receive { x: undefined } (or {})
But I receive { x: {} }

The problem here is that, when I check for the existance of x afterwards, I get false positives.

Is there a good reason for casting this way?
Otherwise I'd like to change this.

[doowb]

I think this is a bug... the only reason I could see it being useful is if you did this...

const obj;
const result = omitDeep(obj, 'y');
console.log(result);
//=> {}

With the change, console.log(result) would be undefined, but I think that's consistent with passing in any other value that's not an object (console.log(omitDeep('foo', 'y') would be foo).

If you'd like to do a PR to return the value instead of {} when undefined and add a test with the case you found, I'll review it.

Also see #6 and change the typeof value === 'undefined' to !value like the PR. Please don't commit a package-lock.json though.

Thanks

[c-vetter]

@doowb
Done 😉

[scamden]

@rasenplanscher any chance you could publish this fix?

@jonschlinkert

[c-vetter]

@scamden fixed in #9
This just needs to get merged 🤔 begs the question if this project is dead 😕

@jonschlinkert Can you merge and publish?

[leMaik]

Came across this bug today. It's sad to see this project die, so I just forked it and published it as @wertarbyte/omit-deep on npm, with @rasenplanscher's PR included.

@jonschlinkert I know maintaining a lot of projects takes a lot of time and effort. I'd be happy to help you maintain this repo/package. 👍

[Murillo2380]

@leMaik also had this bug today. See working example: https://repl.it/@Murillo2380/omit-deep-error

[schester44]

still an issue...