suggestion: use immer in updateSnapshot

[phryneas]

This would be an alternative suggestion to setSnapshot

Checklist:

• If this PR contains changes to the library itself (not necessary for e.g. docs updates), please include a changeset (see CONTRIBUTING.md)
• If this PR is a new feature, please reference an issue where a consensus about the design was reached (not necessary for small changes)
• Make sure all of the significant new logic is covered by tests

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5d89467

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

[phryneas]

The fact that this is safely updatable is highlighted through the types here:

[jerelmiller]

See #11376 (comment)

tl;dr; I'd still like to retain some way of doing a partial update without the need for a callback function to reduce noise for these kinds of updates. Immer may still make sense for this snapshot stuff, so I'm not opposed to introducing it. I just don't want to fully remove this partial update functionality.

Perhaps a different name for this function makes sense?

[jerelmiller]

Discussed in Discord. We're going to avoid this dependency for now and instead rename the functions to replaceSnapshot and mergeSnapshot to better differentiate the behaviors. I will do this over in #11376