fix: hydrate relational values

[kettanaito]

• Fixes Persist extention hydration #343

Root cause

persist/sync strip relational values before storing a record, then restore it via collection.create(), which validates against the schema before relations are initialized. Any required relation is therefore missing at validation time and hydration throws does not match the schema. Existing tests only used .optional() relations, so this went unnoticed.

In the future, it'd be best to migrate all Collection operations to be async and unlock async schema support. That's a breaking change so I'm skipping it for now.

Changes

• Prevent record duplication on sync+persist synergy.
• Enforce sync schemas to guarantee sync hydration.
• Move Collection#sanitizeInitialValues to utils.ts and reuse it in persist: a serialized record is now the same sanitized tree the collection itself validates on update() — relations inlined as foreign-record snapshots, cycles cut identically.
• Store primary keys of the record and every nested snapshot in metadata; deserializeRecord restores them (plus an empty relation map on snapshots so unique relations hydrate).
• createFromSerializedRecord becomes collection.create(deserializeRecord(...)) — relations pick up foreign keys from the snapshots, no post-hoc key patching.
• Bump storage version to 2; skip incompatible persisted data with a warning.
• Defer hydration by a microtask so relations defined right after construction apply to hydrated records (previously relied on validate() being async).
• Tests: Date-through-schema, required relation (persist + sync), unique relation.

[kettanaito]

Released: v1.1.8 🎉

This has been released in v1.1.8.

• 📄 Release notes
• 📦 View on npm

Get these changes by running the following command:

npm i @msw/data@latest

---

Predictable release automation by Release.