Discussion: Should an error in onUpdate trigger the container's error boundary?

[obweger]

Discussion: Should an error in onUpdate trigger the container's error boundary?

[theKashey]

Errors in general should not happen, but if they do - I think it's important to break things at the right place.

Personally - I prefer when things breaks and I "see" it, not then they break silently and I have to idea why UI became glitchy

[albertogasparin]

Good observation, didn't realise that.
The difference is indeed that onInit is called as part of a hook initialisation while onUpdate is called by the subscription, so as part of the schedule/batching process.
I'm not sure however that onInit behaviour is what we should normalise. The reason is that being able to catch it via error boundary is possible only for sync actions. Async actions will always need to be manually caught.

So my worry is that devs might not realise they need an error boundary in the first place. I feel having an out of render error is slightly more annoying to catch but less fatal. And if you use async actions you need to manually handle it regardless.
But open to hear your counter arguments :)

[obweger]

Agree with @theKashey here - my philosophy is also that if something breaks, it should break fully.

For async actions @albertogasparin, I personally think it's fine for these to not trigger the error boundary; after all, I can also trigger any async stuff in a render function and it would also not trigger the error boundary.

My 2c.