@wycats @garybernhardt Oh no, *this* case definitely sucks and is definitely something we often run into. The plan is to have a compiler do this automatically so that it comes up much less often. Unfortunately we haven’t had time to invest into it yet.
@wycats @garybernhardt The other recourse is simply reduce the need for useEffect. I don’t think it’s really the best solution for this case but sometimes structuring code without it is awkward for other reasons. Which we should address.
@wycats @garybernhardt I think this case is a good example of where reactivity is not the right tool. There’s already an explicit signal for when this function should run — the user clicks a button and AJAX response come back. Rederiving this signal through change notifications is lossy by definition.
@wycats @garybernhardt So while we could make reactivity more granular and automate it, I think for this particular case it’s more important to offer a non-reactive solution that’s easy to apply without changing the code structure too much.
