The way ConnectEthereum and CreateSIWEBackupMessage handle SIWE panel state is exactly the same. Additionally getting signature for existing backup message will resuse this logic as well. Therefore this diff extracts it.
Details
Details
- Reviewers
kamil - Commits
- rCOMM094480a836c0: Extract shared logci for SIWE panel state handling
Test that SIWE registration, log in and backup message creation are unchanged.
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
native/account/siwe-hooks.js | ||
---|---|---|
159–165 ↗ | (On Diff #40315) | thinking about adding React.memo here but probably we will not gain much |
native/account/siwe-hooks.js | ||
---|---|---|
159–165 ↗ | (On Diff #40315) | It's probably a good idea. Given the current usages (where we destructure right after calling) there is no advantage to it. But it's good practice, and somebody in the future might call useSIWEPanelState without destructuring immediately |