Paulo Cesar

2: when the source object is empty, it returns undefined (void 0). https://github.com/mariocasciaro/object-path/blob/master/index.js#L198 4: the object isn't empty (obj is `{path: true}`), so it returns itself because the path doesn't...

it's in the 1.0 branch, it's actually 'ready', but the author doesn't want to rely on Typescript, so I need to find an alternative before the release

in the upcoming version you'll be able to augment `object-path` to fit your needs. this would require creating a plugin for object-path and adding another parameter to it, would be...

indeed, I've rewritten the snippet. if you want to test the 1.0.0 to see if solves your problem, check the [1.0.0](https://github.com/mariocasciaro/object-path/tree/1.0.0) branch

it makes sense to have a fourth parameter to change the behavior of the function (like `set` has the internal option `doNotReplace`), it would not break existing code that relies...

that would definitely be a good plugin to have :) 1.0 is embracing modularity, and we will be able to add awesome things using the base of objectPath. we expect...

Well, what about the arguments of those functions? And their context? I think it's possible for you to achieve what you want if add a helper method to `objectPath`: ```...

it mimicks splice, with a default to zero (splice has no default, it removes the item if the value is not set), if you call it without the 1 at...

ok, i will fix something ;) PS: harder than it looks lol

AFAIK, the `objectPath({})` constructor doesn't work on IE8 because it doesn't have `Array.prototype.reduce` and `Object.keys`, but might work with a polyfill. Otherwise it should work. We removed the testling badge...