fix: add try/finally block in withoutSaving method to ensure state re…

[ederzz]

…storation

Description
When i perform some operations and put them in the history stack, then perform some other operations without putting them into the history stack, and then trigger an undo action, this action might fail - for example, it can not find the previous element.The error can cause the restoration of the SAVING state to fail, which in turn leads to the failure of subsequent historyEditor operations to record history.

Issue
Fixes: (link to issue)

Example

Context
I think we should catch the error from the callback of withoutSaving, make it won't affect the restoration of the saving state.

Checks

• The new code matches the existing patterns and styles.
• The tests pass with yarn test.
• The linter passes with yarn lint. (Fix errors with yarn fix.)
• The relevant examples still work. (Run examples with yarn start.)
• You've added a changeset if changing functionality. (Add one with yarn changeset add.)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0568634

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[dylans]

Thanks for the PR, please add a changeset as it's a small change in behavior.

[ederzz]

Thanks for the PR, please add a changeset as it's a small change in behavior.

Fine, got it done!