Juan Tejada ddb661ed37 fix(account-prefs): Update account save logic to prevent incorrect saves ... - This fixes #1354 and #1235 - This issue was caused because the account details preferences component was keeping as state all of the account object fields. `setState` works like `extend`, so when the account changed, state was set to the new set of account fields, but the old values were only removed if they were overriden, and remained the same if the field did not exist in the new state object. Specifically, when a new account was added, setState was called with `{..., defaultAlias: undefined}` which did /not/ remove the the defaultAlias from the previous state. - Switched to managing state with a top level key `account`		2016-02-16 18:03:22 -08:00
..
lib	fix(account-prefs): Update account save logic to prevent incorrect saves	2016-02-16 18:03:22 -08:00
stylesheets	🎨: Smaller buttons, smaller toolbar, smaller text	2016-02-09 19:45:24 -08:00
package.json	fix(license): GPLv3 => GPL-3.0	2015-12-07 10:50:47 -08:00