mirror of
https://github.com/kremalicious/metamask-extension.git
synced 2024-11-22 01:47:00 +01:00
9cfa9ba6b0
In the case where an error is thrown in the UI before initialization has finished, we aren't capturing the application state correctly for Sentry errors. We had a test case for this, but the test case was broken due to a mistake in how the `network-store` was setup (it was not matching the behavior of the real `local-tstore` module). The pre-initialization state capture logic was updated to rely solely upon the `localStore` instance used by Sentry to determine whether the user had opted-in to metrics or not. This simplifies the logic a great deal, removing the need for the `getMostRecentPersistedState` state hook. It also ensures that state is captured corretly pre- initialization in both the background and UI. |
||
|---|---|---|
| .. | ||
| constants | ||
| controllers | ||
| lib | ||
| migrations | ||
| platforms | ||
| app-init.js | ||
| background.js | ||
| contentscript.js | ||
| detect-multiple-instances.js | ||
| detect-multiple-instances.test.js | ||
| disable-console.js | ||
| first-time-state.js | ||
| init-globals.js | ||
| inpage.js | ||
| lockdown-more.js | ||
| lockdown-run.js | ||
| metamask-controller.actions.test.js | ||
| metamask-controller.js | ||
| metamask-controller.test.js | ||
| mmi-keyring-builder-factory.js | ||
| sentry-install.js | ||
| translate.test.ts | ||
| translate.ts | ||
| ui.js | ||
| use-snow.js | ||