Return undefined/default when requesting key nested under null value.

[kalmbach]

Return undefined/default value when requesting for a key nested under a null value.

My logic for this change is:
If we reach an undefined object or the end of the key path (p >= key.length), we return the object in that position, if that object is undefined we return the default value, otherwise we rerturn the object. (including null values)

When we don't reach the end of the key path (p < key.length), it's because a value in between is falsey, in either case that mean the object at the end of the key path is unreachable (undefined) and we should return the default value.

[Closes #9]

[kalmbach]

I have solved the error reported by travis locally installing the uglify-js package (note the diff in the name => uglifyjs)

[developit]

Just a note - I'm pondering this PR and want to merge it, but it won't go into today's release.

[jacktuck]

Could we not just have obj == undefined here and drop the strict equality check? :)

[kalmbach]

I am not following, if we drop the strict equality check it will fail to return a defined key with a null value, and will return the default instead. For example:

var obj = { a: null }
delve(obj, "a", "foo")
=> "foo"

It should have returned null, it's a defined key. It should only return undefined (or the default) when the key is not defined in the object.

The strict equality check is necessary to distinguish undefined keys from the defined keys with null values.
I hope this makes sense.

[jacktuck]

Yeah you're right

[bboydflo]

it would be nice to merge this in :)

[jawadst]

@developit Any chance to merge and release this?

[developit]

Yup. Need to check size.

[developit]

131 bytes means this is only 7 bytes added weight. I'm in.