Feature: useEffectEvent should be useCallback without dependency array about react

[kuchta]

@bayareaunicorn Well, useChildCallback is probably better then useEffectEvent, but considering that people are alredy used to that returned reference from useHooks changes as often as some of it's dependencies, I think that just useCallback without any dependencies would communicate that intention better with respect to already memorized rules.

[kuchta]

@bayareaunicorn That's what it's typically combined with, but if you want to access actual values from a callback provided there, that's when you would want to use it. Despite it's name, experimental useEffectEvent is not an equivalent to useEffect, but to a useCallback, in a sense. That's what this issue is about, that people will probably be confused by it's name...

[bayareaunicorn]

I see perhaps useChildCallback or useCallbackChild would be a better fit?

useCallback Use Case: It is used to prevent unnecessary re-renders of child components by memoizing a function instance and changing the callback only when one of its dependencies changes .
useEffectEvent Use Case: It provides a more powerful alternative to useCallback with no dependencies, allowing for constant reference to a function and preventing unnecessary re-renders of child components

[Gregoor]

I think that would be unwise, the rules of useEffectEvent are that it's only to be called from effects and not passed to child components. useCallback does not have that limitation. Having semantics diverge this massively by just (not) passing a dependency array in, would lead to confusion.

[Gregoor]

Yeah that maps closer to my conceptualization of it as well. I think the React team's lingo might diverge here from ours though. I would be curious to read a team member's take on this.

[eqpoqpe]

um, cool

[bayareaunicorn]

Seems useless why not just pass an empty array in your useEffect to render only once?

[kuchta]

@Gregoor Fair point. So maybe useEffectCallback would be better choice, since calling it Event is quite misleading as well...