Closed oigewan closed 8 years ago
Looking through the issues, someone else already had this problem. PR fixes #72
Hi @oigewan
Thanks for the PR, it will be merged on the next release. I wanted to publish the next version today but I got stuck with some major changes. I hope it can be released soon.
Cheers
No worries, man. Glad to see there's still active development. We're pointing to our fork with the patch for now just to allow us to keep moving. I'll check back in a week or two to see about getting back onto the main repo.
This is a great tool. Thanks for the hard work.
Bug: If using a pivot to update multiple nested objects and the call to
.set()
would not result in a change, the node is returned instead of the pivot.Changes:
.set()
API, check for a pivot. Return it if it's there and return the node if it's not.