Paulo Cesar

ok that makes sense, for the sake of simplicity. maybe test if path is an array, and then don't test it if it's empty, shouldn't change anything in current tests...

@mariocasciaro I noticed that if we don't pass a intermediate flag to the recursive calls, the path setting of value for non-existing paths 'throws'. Like, the intermediate non-existing path of...

I was thinking of something like this. You can extend objectPath and receive an "object environment" when you pass in a decorator function (like angular does): ``` js // promise-object-path.js...

yeah, a `(new objectPath()).extend` could work, make it a prototype function instead of a static member of the `objectPath` global. plus it could have it's own set of options, that...

I'd love to have the green light to go hack and happy to make it to a 1.0.0 version :facepunch: it would automatically close at least 5 open issues

the current global won't change. the objectPath global will be an instanced version of the internal objectPath class with default options. under the hood, the average library consumer won't notice...

Well, I'm thinking ahead, when ES6 is the norm. The way I proposed, you can still use extend once and it will be global (since you are modifying an instance,...

there's a fundamental flaw in keeping `objectPath({})`, that is the anti-pattern of returning from inside a constructor. the "wrapping" (if we may call it that) is (ab)using the fact that...

alright, I'll be using the 1.0.0 branch I created. I'll try to do the benchmarks and the 1.0.0 this weekend. I can also document the code using jsdoc if you...

Preliminary rewrite done (the basic funcionality). Extend not done yet https://travis-ci.org/mariocasciaro/object-path/builds/62853434 Tests weren't changed, only for `objectPath({}) -> objectPath.bind({})`. I'll then comment the code, add the rest of the tests...