fix(persisted-state): write state to storage even if only a nested property is changed. fixes #224

[gyszalai]

Integrated Rich Harris's proxy solution to solve watching nested properties:
https://github.com/Rich-Harris/local-storage-test/blob/main/src/lib/storage.svelte.ts

Had to update existing tests as the getter for current always deserializes the state from storage.

[changeset-bot]

⚠️ No Changeset found

Latest commit: bc1ce7e

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

[webJose]

I would say this is not the best approach. One can leverage the deep reactive nature of Svelte v5 and have an $effect serialize and store the value. This should pick up on any changed property along the chain of objects.

[gyszalai]

I would say this is not the best approach. One can leverage the deep reactive nature of Svelte v5 and have an $effect serialize and store the value. This should pick up on any changed property along the chain of objects.

@webJose you are absolutely right! My first solution was to use $effect, it was much simpler. However, with that solution the state is not written to the storage synchronously, but asynchronously in the next tick and this broke all tests.