Right now, all local state (aside from partial proofs) are stored under a single wallet object. See https://github.com/polymorpher/one-wallet/blob/master/code/client/src/state/modules/wallet/reducers.js
This causes several issues. For example, #192, and that it is very easy to mess up the entire state in a simple, async local update, such as changing a simple flag (e.g. whether wallet QR code was saved) in one single wallet. Global states (such as address book) and states of each individual wallet are stored together under this object.
This should not be the case. We should refactor the whole redux flow and keep each storage object as minimal as possible.
Right now, all local state (aside from partial proofs) are stored under a single
walletobject. See https://github.com/polymorpher/one-wallet/blob/master/code/client/src/state/modules/wallet/reducers.jsThis causes several issues. For example, #192, and that it is very easy to mess up the entire state in a simple, async local update, such as changing a simple flag (e.g. whether wallet QR code was saved) in one single wallet. Global states (such as address book) and states of each individual wallet are stored together under this object.
This should not be the case. We should refactor the whole redux flow and keep each storage object as minimal as possible.