mirror of
https://github.com/kremalicious/metamask-extension.git
synced 2024-10-22 11:22:43 +02:00
9847179f54
We now set the network status to "unknown" rather than "unavailable" when the network ID is invalid. This better reflects what we know when this happens, and it makes the network controller better aligned with the core network controller. This was accomplished by using a regular error for the network ID assertion rather than using `assert` directly. `assert` would throw an error with a `code` property, which resutled in us treating it like an RPC error. This isn't tested, but it was found in the course of porting unit tests from core to extension. It will be covered by these tests, which will be added in the next PR. This change should have no functional impact because we treat these two network statuses as equivalent. The distinction between unknown and unavailable is useful only for debugging. |
||
|---|---|---|
| .. | ||
| account-import-strategies | ||
| 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 | ||
| sentry-install.js | ||
| ui.js | ||
| use-snow.js | ||