tangerine-wallet-browser - Tangerine fork of MetaMask browser extension (https://github.com/tangerine-network/tangerine-wallet-browser)

index : tangerine-wallet-browser

Tangerine fork of MetaMask browser extension (https://github.com/tangerine-network/tangerine-wallet-browser)

about summary refs log tree commit diff stats

path: root/app/scripts/lib/config-manager.js

	Commit message (Collapse)	Author	Age	Files	Lines
*	idmgmt - eth_sign support + notifications	kumavis	2016-04-29	1	-5/+77
\|
*	Persist selected account	Dan Finlay	2016-04-26	1	-0/+11
\| \| \| \| \| \|	When selecting an account, we now persist the selection to the `configManager`, so the selection can be restored when re-unlocking Metamask. Also found the bug where `rawtestrpc` was still being used as a default, and fixed it!
*	Store metamaskId on metaTx instead of getTxWithParams method.	Dan Finlay	2016-04-21	1	-10/+0
\|
*	Fix config manager method	Dan Finlay	2016-04-20	1	-1/+1
\|
*	Add extra tx methods to configManager	Dan Finlay	2016-04-20	1	-3/+25
\|
*	Persist transactions to config-manager	Dan Finlay	2016-04-19	1	-0/+50
\| \| \| \| \| \| \| \|	Transactions are now stored, and are never deleted, they only have their status updated. We can add deleting later if we'd like. I've hacked on emitting the new unconfirmedTx key to the UI in the format it received before, I want Aaron's opinion on where I should actually do that.
*	inpage - use publicConfigStore for selectedAccount and sync provider	kumavis	2016-04-16	1	-0/+27
\|
*	Point rawtestrpc at new testrpc	Dan Finlay	2016-04-13	1	-1/+1
\|
*	Migrate etherscan configs to our new production RPC.	Dan Finlay	2016-04-13	1	-3/+7
\|
*	Revert "Revert "Etherscan provider""	Dan Finlay	2016-04-01	1	-9/+22
\|
*	Revert "Etherscan provider"	Dan Finlay	2016-04-01	1	-22/+9
\|
*	First naive pass at implementing etherscan provider (not working)	Dan Finlay	2016-04-01	1	-9/+22
\| \| \| \|	Committing and pushing to get feedback.
*	Do not cache the seed, retrieve it from the decrypted wallet	Dan Finlay	2016-04-01	1	-9/+5
\|
*	Made configuration migrateable	Dan Finlay	2016-03-31	1	-0/+161
	Abstract all configuration data into a singleton called `configManager`, who is responsible for reading and writing to the persisted storage (localStorage, in our case). Uses my new module [pojo-migrator](https://www.npmjs.com/package/pojo-migrator), and wraps it with the `ConfigManager` class, which we can hang any state setting or getting methods we need. By keeping all the persisted state in one place, we can stabilize its outward-facing API, making the interactions increasingly atomic, which will allow us to add features that require restructuring the persisted data in the long term without having to rewrite UI or even `background.js` code. All the restructuring and data-type management is kept in one neat little place. This should make it very easy to add new configuration options like user-configured providers, per-domain vaults, and more! I know this doesn't seem like a big user-facing feature, but we have a big laundry list of features that I think this will really help streamline.