improve the documentation for the eager connect and inactive listener code
Open
Nobody has claimed this yet.
p2
refactor
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
currently i'm not sure why this code is calling activate when chain or accounts changed, trying to debug the walletconnect issue
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading src/hooks/web3.ts lines 52-94, focusing on the eager connect and inactive listener code. Determine why activate is called when the chain or accounts change, then document that behavior and its relevance to debugging the WalletConnect issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100