liftedinit / liftedinit/alberto
Display toast/alert on web3auth connect errors
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
We're getting the following error on social login when a login fails to connect to web3auth. As of now, there's only a console error message when this happens. We should display a toast or alert to the user when there is a connection error and provide instructions such as refresh your browser, retry, etc.
https://github.com/liftedinit/alberto/blob/3b8894ac14cb3aeb0fd5c3d4ed71ac2996770ab8/src/features/accounts/components/social-login/social-login.tsx#L101
```
social-login.tsx:101 connectTo error WalletLoginError: Wallet is not connectedNo wallet is connected
connectTo error WalletLoginError: Wallet is not connectedNo wallet is connected
at Function.value (index.ts:143:12)
at Function.value (index.ts:155:29)
at r. (core.ts:175:104)
at d (regeneratorRuntime.js:72:17)
at Generator._invoke (regeneratorRuntime.js:55:24)
at Generator.next (regeneratorRuntime.js:97:21)
at r (asyncToGenerator.js:3:20)
at s (asyncToGenerator.js:22:9)
at asyncToGenerator.js:27:7
at new Promise ()
```
Contributor guide
Research direction
Start at src/features/accounts/components/social-login/social-login.tsx around line 101, where the web3auth connection error is logged. Inspect the surrounding social-login error handling and existing user-notification patterns, then show refresh and retry guidance when connection fails. Done means the failure gives the user a toast or alert instead of only a console error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100