{"action":"opened","issue":{"url":"https://api.github.com/repos/ohler55/oj/issues/290","repository_url":"https://api.github.com/repos/ohler55/oj","labels_url":"https://api.github.com/repos/ohler55/oj/issues/290/labels{/name}","comments_url":"https://api.github.com/repos/ohler55/oj/issues/290/comments","events_url":"https://api.github.com/repos/ohler55/oj/issues/290/events","html_url":"https://github.com/ohler55/oj/issues/290","id":133985824,"number":290,"title":"Raise JSON::ParserError when Oj::ParseError would be raised for mimic_JSON()?","user":{"login":"RST-J","id":4967885,"avatar_url":"https://avatars.githubusercontent.com/u/4967885?v=3","gravatar_id":"","url":"https://api.github.com/users/RST-J","html_url":"https://github.com/RST-J","followers_url":"https://api.github.com/users/RST-J/followers","following_url":"https://api.github.com/users/RST-J/following{/other_user}","gists_url":"https://api.github.com/users/RST-J/gists{/gist_id}","starred_url":"https://api.github.com/users/RST-J/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RST-J/subscriptions","organizations_url":"https://api.github.com/users/RST-J/orgs","repos_url":"https://api.github.com/users/RST-J/repos","events_url":"https://api.github.com/users/RST-J/events{/privacy}","received_events_url":"https://api.github.com/users/RST-J/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-02-16T13:47:14Z","updated_at":"2016-02-16T13:47:14Z","closed_at":null,"body":"Hello,\r\nI encountered an issue when using Oj as replacement for the default JSON parser via `mimic_JSON` which is that error handlers in other code (e.g. other gems) which assume that they have to handle a `JSON::ParserError` error won't be able to handle the situation as they receive an `Oj::ParseError`.\r\nSo my question is: Wouldn't it be reasonable to raise a `JSON::ParserError` when `mimic_JSON` was called instead of Oj's error class? Or, as I don't know about internals, somehow ensure that the raised error is a subclass of `JSON::ParserError` in this situation?"}}