-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
get blows up when trying to extract path from a null value - failed gracefully in 1.2.0 #36
Comments
Please confirm with today's release v2.1.0. I'll create a proof under |
I will test it out this week - thanks for the quick reply. |
Fixed in v2.1.1 |
The issue is resolved in 2.1.1. I am going to go with 2.2.0 since it fixes the extra console log that was in the util file. Thanks for taking care of this quickly! Excited to upgrade and get the typescript support. Appreciate you and your work on this library! 🙂 |
I recently upgraded to 1.3.1 so I could use this library with Typescript, but it seems like what used to fail gracefully is now blowing up.
If I have an object like:
With 1.2.0 - if I tried to get the field "/employee/st_price" - it would fail gracefully and return undefined
With 1.3.1 - it blows up saying it can't find "st_price" in
null
The text was updated successfully, but these errors were encountered: