Content pfp
Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions

Steve pfp
Steve
@stevedylandev.eth
Idk what's worse, 15 useStates in the root of an app or this many useEffect dependencies 😭
9 replies
4 recasts
27 reactions

Joshua Hyde (he/him) pfp
Joshua Hyde (he/him)
@jrh3k5.eth
Me burning up a user's CPU when I don't have to pay for the compute time
1 reply
0 recast
4 reactions

Rafi pfp
Rafi
@rafi
I don’t like it but I liked it as a sign of sympathy
1 reply
0 recast
2 reactions

Phil Cockfield pfp
Phil Cockfield
@pjc
If I had to choose between two 'mares, I'd personally go with refactoring the useEffect's first (if even possible 😵🤣). There be so many dragon's in and around useEffect - <sigh>
1 reply
0 recast
4 reactions

Darryl Yeo 🛠️ pfp
Darryl Yeo 🛠️
@darrylyeo
Many such cases :( https://warpcast.com/darrylyeo/0xe28f80c1
0 reply
0 recast
2 reactions

typeof.eth 🔵 pfp
typeof.eth 🔵
@typeof.eth
If setAddress and setInitialized are the result of the useStates you mentioned, you should be able to remove them from the dep array
0 reply
0 recast
2 reactions

Barbs pfp
Barbs
@bbq
this could be a useful read, some older approaches with state/effects are obsolete these days https://react.dev/learn/you-might-not-need-an-effect
0 reply
0 recast
1 reaction

Royal pfp
Royal
@royalaid.eth
And all the use callbacks for the fns
0 reply
0 recast
1 reaction

Daniel Ribeirinha-Braga pfp
Daniel Ribeirinha-Braga
@dbragz.eth
Personally I think the worst option would be the useEffect. ❌ In that function you need to account for all those variable transition changes and that sounds like a nightmare. 😱 If the useState is being used you can isolate each variable specifically. 🧩
0 reply
0 recast
0 reaction

Leonard Milea pfp
Leonard Milea
@leonort.eth
Good thing about not working with other devs is i can avoid all my pet peeves by not including no garbage like this :)
0 reply
0 recast
0 reaction