{"action":"closed","issue":{"url":"https://api.github.com/repos/gaearon/redux-devtools/issues/269","repository_url":"https://api.github.com/repos/gaearon/redux-devtools","labels_url":"https://api.github.com/repos/gaearon/redux-devtools/issues/269/labels{/name}","comments_url":"https://api.github.com/repos/gaearon/redux-devtools/issues/269/comments","events_url":"https://api.github.com/repos/gaearon/redux-devtools/issues/269/events","html_url":"https://github.com/gaearon/redux-devtools/issues/269","id":148799266,"number":269,"title":"Don't catch errors?","user":{"login":"DelvarWorld","id":79215,"avatar_url":"https://avatars.githubusercontent.com/u/79215?v=3","gravatar_id":"","url":"https://api.github.com/users/DelvarWorld","html_url":"https://github.com/DelvarWorld","followers_url":"https://api.github.com/users/DelvarWorld/followers","following_url":"https://api.github.com/users/DelvarWorld/following{/other_user}","gists_url":"https://api.github.com/users/DelvarWorld/gists{/gist_id}","starred_url":"https://api.github.com/users/DelvarWorld/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DelvarWorld/subscriptions","organizations_url":"https://api.github.com/users/DelvarWorld/orgs","repos_url":"https://api.github.com/users/DelvarWorld/repos","events_url":"https://api.github.com/users/DelvarWorld/events{/privacy}","received_events_url":"https://api.github.com/users/DelvarWorld/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-04-16T00:27:38Z","updated_at":"2016-04-18T22:53:28Z","closed_at":"2016-04-18T22:53:28Z","body":"This might be more of a suggestion or personal preference, but what is the motivation for catching errors produced by actions? https://github.com/gaearon/redux-devtools/blob/master/src/instrument.js#L78-L80\r\n\r\nThis means if an action causes an error in *any* other part of my application, like a component remounting, then the error will be caught, the stack trace lost, and then error in a different place.\r\n\r\nThis makes it more difficult to find errors in dev. It also means that the \"pause on exceptions\" setting can't be used without \"pause on uncaught exceptions\" - which, if on app startup (page refresh), means you have to step through about 30 babel/webpack intentionally caught errors to see the error in question.\r\n\r\nFor me personally it would be nicer for local app development and debugging if error stack traces were preserved."}}