First resetKeys update ignored when error triggered on mount

[wild-lotus]

• react-error-boundary version: 3.1.0
• node version: 12.16.1
• yarn version: 1.22.5

What you did:

I use ErrorBoundary with resetKeys, with the error being triggered on ErrorBoundarymount. Then I trigger a reset via resetKeys

What happened:

The ErrorBoundary error state is not reset until the second resetKeys update.

Reproduction repository:

https://codesandbox.io/s/react-error-boundaryignored-update-issue-fcfyi?file=/src/App.js
This is the same code as in Error Recovery example, but with explode state initialized as true.
Try clicking "toggle explode" button right after the initial render: it does not get reset.

Problem description:

this.updatedWithError flag is not set on component mount, only on component update, so if the error is triggered on component mount, 2 extra updates are needed instead of one. The first one sets the this.updatedWithError and the second ones resets the state.

Suggested solution:

Adding:

  componentDidMount() {
    const {error} = this.state
    if (error !== null) {
      this.updatedWithError = true
    }
  }

[wild-lotus]

Silly me, I just realised this is a duplicate from #74. 🤦
I suggest a different solution though, happy to attempt a PR if you see it fit.

[github-actions]

🎉 This issue has been resolved in version 3.1.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀