Change Details

`npm test` `npm run extension` navigate to `brave://extensions` and update ``` cd modules/cashtab-connect/demo npm start ``` navigate to `localhost:3000`, check logs for extension, confirm migration, check that you can just see your wallets as before, confirm address sharing still works

`npm test` `npm run extension` navigate to `brave://extensions` and update ``` cd modules/cashtab-connect/demo npm start ``` navigate to `localhost:3000`, check logs for extension, confirm migration, check that you can just see your wallets as before, confirm address sharing still works Migration risk is mitigated here by not wiping localforage. It's not practical to test migration in unit tests / integration tests as we end up mocking all of the storage APIs and then ... "hey look the mock was called" I did a few migrations including settings, contacts, multiple wallets by building old extension, setting it up, then installing the new one and opening it, checking the logs.

`npm test` `npm run extension` navigate to `brave://extensions` and update ``` cd modules/cashtab-connect/demo npm start ``` navigate to `localhost:3000`, check logs for extension, confirm migration, check that you can just see your wallets as before, confirm address sharing still works Migration risk is mitigated here by not wiping localforage. It's not practical to test migration in unit tests / integration tests as we end up mocking all of the storage APIs and then ... "hey look the mock was called" I did a few migrations including settings, contacts, multiple wallets by building old extension, setting it up, then installing the new one and opening it, checking the logs.