Closed JakeDluhy closed 7 years ago
I was expecting that if my obj was bad/corrupted for whatever reason, then onError would be called when attempting to parse it. However that is not the case, it just throws an exception.
I'd be willing to submit a PR for this
Changes in #14. Would be willing to make them again once #12 gets merged in.
@sohamkamani can you release a new npm version? And then we can close this out
npm
Done 👍 Thanks for the help!
No problem!
I was expecting that if my obj was bad/corrupted for whatever reason, then onError would be called when attempting to parse it. However that is not the case, it just throws an exception.
I'd be willing to submit a PR for this