A Metamask fork with Infura removed and default networks editable

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Mark Stacey 63633635ab Fix order of accounts in `eth_accounts` response (#8342) ... * Fix order of accounts in `eth_accounts` response The accounts returned by `eth_accounts` were in a fixed order - the order in which the keyring returned them - rather than ordered with the selected account first. The accounts returned by the `accountsChanged` event were ordered with the selected account first, but the same order wasn't used for `eth_accounts`. We needed to store additional state in order to determine the correct account order correctly on all dapps. We had only been storing the current selected account, but since we also need to determine the primary account per dapp (i.e. the last "selected" account among the accounts exposed to that dapp), that wasn't enough. A `lastSelected` property has been added to each identity in the preferences controller to keep track of the last selected time. This property is set to the current time (in milliseconds) whenever a new selection is made. The accounts returned with `accountsChanged` and by `eth_accounts` are both ordered by this property. The `updatePermittedAccounts` function was merged with the internal methods for responding to account selection, to keep things simpler. It wasn't called externally anyway, so it wasn't needed in the public API. * Remove caveat update upon change in selected account The order of accounts in the caveat isn't meaningful, so the caveat doesn't need to be updated when the accounts get re-ordered. * Emit event regardless of account order Now that we're no longer relying upon the caveat for the account order, we also have no way of knowing if a particular account selection resulted in a change in order or not. The notification is now emitted whenever an exposed account is selected - even if the order stayed the same. The inpage provider currently caches the account order, so it can be relied upon to ignore these redundant events. We were already emiting redundant `accountsChanged` events in some cases anyway.		5 years ago
..
network	Update ESLint rules for test suite (#8023)	5 years ago
permissions	Fix order of accounts in `eth_accounts` response (#8342)	5 years ago
transactions	LoginPerSite: Support multiple accounts without automatic switching (#8079)	5 years ago
balance-controller.spec.js	Update ESLint rules for test suite (#8023)	5 years ago
cached-balances-test.js	Update ESLint rules for test suite (#8023)	5 years ago
detect-tokens-test.js	Cleanup detect-tokens controller and tests (#8329)	5 years ago
ens-controller-test.js	Update ESLint rules for test suite (#8023)	5 years ago
incoming-transactions-test.js	Prevent accidental use of globals (#8340)	5 years ago
infura-controller-test.js	Remove unused sinon sandboxes (#8063)	5 years ago
metamask-controller-test.js	Fix order of accounts in `eth_accounts` response (#8342)	5 years ago
preferences-controller-test.js	Update PreferencesController tests (#8328)	5 years ago
token-rates-controller.js	Update ESLint rules for test suite (#8023)	5 years ago