Throwing an exception is for exceptional cases. Not finding the target data doesn't feel like an exceptional case, particularly if I'm going to use the pointer as a filter to select from a set of objects that might match.
Return null instead of throwing an exception when the pointer is vali…
…d, but the doc does not contain the given value.
Note to self. this breaks BC and we must bump to version 2.x.y.
Agree with BC issue. Wait for compile patch before releasing 2.x though?
Can do, but no biggie, I am fast and loose with major version numbers, I wouldn’t mind shipping 2.0.0 tonight and 3.0.0 tomorrow ;)
I’ll play it by ear if anyone wants this in a release asap, if not it can wait.
I can use this fix. What's the compile patch?
It was @hildjj that said "Wait for compile patch before releasing 2.x though?"
Another note, it ought to return undefined rather than null. That would be a convenient way to differentiate between finding "null" and not finding the key at all.
I was talking about hildjj@1c373d5
@benatkin good point, wanna open a new issue?