DEV Community


Discussion on: How to build bulletproof react components

eliseumds profile image
Eliseu Monar dos Santos • Edited

Not really. As a newcomer reading the docs, you find an example where setCount(count + 1) is used instead of a callback: Even though the API Reference indeed recommends using a callback, it's not very clear why.

arhsim profile image

Completely agree. In fact, in a function component the callback setup would also not help and the callbacks should be defined using a useCallback.

jsco profile image
Jesco Wuester Author

It's mostly for when the value updates extremely fast. That way even when 2 rerenders get batched together the value stays correct. I figured it wouldn't really matter for my example tho

Thread Thread
marklai1998 profile image
Mark Lai • Edited

That's what I meant to say
When I was a junior react developer, I always told to use callback whenever the new value is referencing the old one.
And indeed, doing simple setState it doesn't matter

But as the app grows, there are 2 cases that may cause the setState incorrect

  1. state update really fast
  2. multiple setState is called in different places

But I still tend to use callback whenever possible, because it's hard to justify when is okay to use the value straight away when the code is complex
Also when you are doing a large refactor, you can't rethink to make sure every single setState is safe

After the release of React hooks, I see more ppl write code that has a lot of side effect, useEffect everywhere, thus I think its more important to enforce this rule, otherwise ppl may fix a lot of silly bugs