Order of life cycle method calls with error boundaries is unexpected

I have a requirement for my app to track when a component has completed rendering and whether the render ended in success or failure. I expected to be able to use the componentDidMount/componentDidUpdate life cycle methods along with an error boundary's componentDidCatch method to handle both success and failure cases.

However, I am noticing that the order of the life cycle methods is not what I expect. When an exception is raised within a child component in the error boundary, the component's componentDidMount/componentDidUpdate method will get called first before componentDidCatch. So I can't simply use componentDidMount/componentDidUpdate to determine that my scenario ended in success.

Is this a bug? How would I go about achieving this scenario?

Non è indicato alcun file, test o punto di ingresso. Inizia individuando la documentazione di React relativa a componentDidMount, componentDidUpdate, componentDidCatch e agli error boundary, quindi verifica l'ordine del ciclo di vita segnalato. Il lavoro è completato quando il comportamento previsto e un modo supportato per distinguere tra rendering riuscito e fallito sono documentati chiaramente.