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?

未指定文件、测试或入口点。首先找到涵盖 componentDidMount、componentDidUpdate、componentDidCatch 和错误边界的 React 文档，然后验证所报告的生命周期顺序。当预期行为以及一种受支持的区分渲染成功与失败的方法都得到清晰记录时，即可视为完成。