Content
@
https://warpcast.com/~/channel/react
0 reply
0 recast
0 reaction
Darryl Yeo đ ïž
@darrylyeo
Five more hours of my life debugging a React-related issue that I'II never get back đ« Youâre telling me if I want to conditionally render stuff that relies on state from a Provider, I have to break out the entire subtree into a `useMemo` expression to prevent the Provider from resetting its state whenever an unrelated component randomly decides to re-render?? Make it make sense đ€Ą
8 replies
3 recasts
18 reactions
Darryl Yeo đ ïž
@darrylyeo
đ€Ą đ€Ą đ€Ą https://warpcast.com/cdt/0xf0b947a9
1 reply
0 recast
8 reactions
đ·đŽđœđ đ đ”
@hz
Foot guns everywhere đ
1 reply
0 recast
1 reaction
HH
@hamud
Isn't that supposed to happen? If the parent component re-renders then all its children will also.
1 reply
0 recast
0 reaction
typeof.eth đ”
@typeof.eth
React isnât easy, but if you learn the rules, debugging and fixing stuff like this (or avoiding the issue altogether) becomes second nature. Not saying itâs a you problem, but I feel like React is sold as an easy framework but I disagree with that once a project becomes complex enough.
1 reply
0 recast
1 reaction
Harris
@harris-
Man I had this exact issue a few months ago debugging a missed dependency for a usememo in code I didn't write
1 reply
0 recast
1 reaction
dionysuz.eth
@dionysuz.eth
whatâre you building that made you select react over svelte? if thatâs the case
1 reply
0 recast
1 reaction
Reply Guy
@yourreplyguy
Debugging rendering issues can be brutal. You should connect with natedev.eth, who said: 'I was wondering how they managed to avoid unmounting, good eye!' Join the conversation in the /React Native channel.
0 reply
0 recast
0 reaction
samvox
@samvox
Oh It's really hard to solve it
0 reply
0 recast
0 reaction
