Pob
@pobch.bsky.social
JavaScript, TypeScript, React, Go
🖖 crispyscript.com
🖖 crispyscript.com
State setter in React needs to be a pure function. Period.
I usually see this anti-pattern from the code review.
onClick prop in the example may contain another setState() or other side-effects from the parent. Be cautious and don’t call any event handlers inside a setter.
I usually see this anti-pattern from the code review.
onClick prop in the example may contain another setState() or other side-effects from the parent. Be cautious and don’t call any event handlers inside a setter.
February 4, 2025 at 11:45 AM
State setter in React needs to be a pure function. Period.
I usually see this anti-pattern from the code review.
onClick prop in the example may contain another setState() or other side-effects from the parent. Be cautious and don’t call any event handlers inside a setter.
I usually see this anti-pattern from the code review.
onClick prop in the example may contain another setState() or other side-effects from the parent. Be cautious and don’t call any event handlers inside a setter.
Colleague: Wow, your side project looks great
Me: Thanksss 😊
Colleague: The code would be nice & clean. Can I take a look?
Me:
Me: Thanksss 😊
Colleague: The code would be nice & clean. Can I take a look?
Me:
November 5, 2024 at 4:49 PM
Colleague: Wow, your side project looks great
Me: Thanksss 😊
Colleague: The code would be nice & clean. Can I take a look?
Me:
Me: Thanksss 😊
Colleague: The code would be nice & clean. Can I take a look?
Me: