{"action":"created","issue":{"url":"https://api.github.com/repos/troessner/reek/issues/809","labels_url":"https://api.github.com/repos/troessner/reek/issues/809/labels{/name}","comments_url":"https://api.github.com/repos/troessner/reek/issues/809/comments","events_url":"https://api.github.com/repos/troessner/reek/issues/809/events","html_url":"https://github.com/troessner/reek/issues/809","id":124542500,"number":809,"title":"Wrap exceptions under ReekException","user":{"login":"troessner","id":271109,"avatar_url":"https://avatars.githubusercontent.com/u/271109?v=3","gravatar_id":"","url":"https://api.github.com/users/troessner","html_url":"https://github.com/troessner","followers_url":"https://api.github.com/users/troessner/followers","following_url":"https://api.github.com/users/troessner/following{/other_user}","gists_url":"https://api.github.com/users/troessner/gists{/gist_id}","starred_url":"https://api.github.com/users/troessner/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/troessner/subscriptions","organizations_url":"https://api.github.com/users/troessner/orgs","repos_url":"https://api.github.com/users/troessner/repos","events_url":"https://api.github.com/users/troessner/events{/privacy}","received_events_url":"https://api.github.com/users/troessner/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/troessner/reek/labels/discussion","name":"discussion","color":"eb6420"},{"url":"https://api.github.com/repos/troessner/reek/labels/feature","name":"feature","color":"7af07a"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2016-01-01T11:56:11Z","updated_at":"2016-01-04T19:33:06Z","closed_at":null,"body":"The title says it all - I believe we should wrap all exception that `Reek` explicitly might throw under `ReekException` and store the original exception as a attribute like [here](http://devblog.avdi.org/2013/12/25/exception-causes-in-ruby-2-1/) or use `Exception#cause`. \r\nThat provides a cleaner separation of concerns to the user and will make debugging on the user end simpler (because it's clearer where the problem originates).\r\n\r\nWDYT?"},"comment":{"url":"https://api.github.com/repos/troessner/reek/issues/comments/168778954","html_url":"https://github.com/troessner/reek/issues/809#issuecomment-168778954","issue_url":"https://api.github.com/repos/troessner/reek/issues/809","id":168778954,"user":{"login":"mvz","id":10898,"avatar_url":"https://avatars.githubusercontent.com/u/10898?v=3","gravatar_id":"","url":"https://api.github.com/users/mvz","html_url":"https://github.com/mvz","followers_url":"https://api.github.com/users/mvz/followers","following_url":"https://api.github.com/users/mvz/following{/other_user}","gists_url":"https://api.github.com/users/mvz/gists{/gist_id}","starred_url":"https://api.github.com/users/mvz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mvz/subscriptions","organizations_url":"https://api.github.com/users/mvz/orgs","repos_url":"https://api.github.com/users/mvz/repos","events_url":"https://api.github.com/users/mvz/events{/privacy}","received_events_url":"https://api.github.com/users/mvz/received_events","type":"User","site_admin":false},"created_at":"2016-01-04T19:33:06Z","updated_at":"2016-01-04T19:33:06Z","body":"I'm sure we'll figure those details out :smile:."}}