thrown errors in context lifecycle method renders nothing (errorComponent)
Hi, the route
context() lifecycle method "hangs" when thrown errors happen, leading to no content being rendered at all. I expect the errorBoundary to show, much like it happens in beforeLoad. Is this intentional?2 Replies
fascinating-indigo•2mo ago
FYI context() is not a public API, it will be changed
rival-blackOP•2mo ago
Alright, make sense. Thanks for responding to this. We'll be moving our context results down to
beforeLoad then. Cheers.