fix: reset the error when mutate succeeded

[koba04]

fixes #2586

Currently, there is no way to reset the error without revalidation. However, in v1, we can do this by mutate(v => v, false) that @shuding mentioned at #193 (comment).

That change was introduced at #2182 is to avoid propagating mutate errors to fetching errors(global cache). This this change makes sense, but the behavior that mutate clears error when it succeeds also makes sense because we no longer need the error after mutate succeeded.

@shuding What do you think?

If this doesn't make sense, I think it would be nice if we provide another way to reset error without revalidation.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 4ec7cff:

Sandbox	Source
SWR-Basic	Configuration
SWR-States	Configuration
SWR-Infinite	Configuration
SWR-SSR	Configuration
musing-thompson-v6u94v	Issue #2586

[pkunat]

Hello @shuding & @huozhi,
Are you planning to add this fix to 2.2.0/2.2.1? I couldn't find it in the changelog and the code is also not on any of the beta branches. I tried to use the main branch, but got stuck trying to find a way to access the global mutate function, which got moved to modules that are no longer exported (intentional?).

[huozhi]

@pkunat sorry for missing the changelog, just published the release log of v2.2.0-beta.1. We're testing for v2.2.0 now, will release soon