@weaverse/next 0.1.0-alpha.18 → 0.1.0-alpha.19

package/dist/index.mjs

@@ -1,5 +1,5 @@
-import { buildWeaverseNextRequestInfo, DEFAULT_REVALIDATE_ENDPOINT, revalidateWeaverseNextItem, generateDataFromSchema } from './chunk-HRNAW6CA.mjs';
-export { DEFAULT_REVALIDATE_ENDPOINT, buildWeaverseNextRequestInfo, buildWeaverseNextRevalidateRouteContext, formatWeaverseNextSeoMetadata, generateDataFromSchema, getWeaverseNextSeoMetadata, revalidateWeaverseNextItem, runWeaverseComponentLoaders } from './chunk-HRNAW6CA.mjs';
+import { buildWeaverseNextRequestInfo, DEFAULT_REVALIDATE_ENDPOINT, revalidateWeaverseNextItem, generateDataFromSchema } from './chunk-LH6AAEIK.mjs';
+export { DEFAULT_REVALIDATE_ENDPOINT, buildWeaverseNextRequestInfo, buildWeaverseNextRevalidateRouteContext, formatWeaverseNextSeoMetadata, generateDataFromSchema, getWeaverseNextSeoMetadata, revalidateWeaverseNextItem, runWeaverseComponentLoaders } from './chunk-LH6AAEIK.mjs';
 import { WeaverseRoot, Weaverse, WeaverseItemStore, useSafeExternalStore } from '@weaverse/react';
 export { isBrowser, isIframe, useChildInstances, useItemInstance, useParentInstance, useWeaverse } from '@weaverse/react';
 import { createSchema } from '@weaverse/schema';
@@ -44,15 +44,31 @@ var WeaverseNextItem = class extends WeaverseItemStore {
   /**
    * Flatten nested `data` on updates exactly like the constructor does. Core's
    * `initProject()` calls `setData(item)` when a new runtime serves a page
-   * whose item instances already exist (e.g. locale/client navigation), and
-   * the inherited shallow merge would leave stale top-level props behind.
-   * Assigning through the inherited `data` setter swaps the `_store` ref,
-   * which invalidates the memoized snapshot below. The subscriber emit is
-   * queued instead of fired when a render-phase deferral is active (see
-   * `collectDeferredItemUpdates`).
+   * whose item instances already exist (e.g. locale/client navigation).
+   *
+   * A complete serialized item (it carries `id` and `type`; core's
+   * `initProject()` always passes one) replaces the store the way the
+   * constructor builds it: the schema defaults of the item's own `type` — the
+   * Builder can replace a section in place, keeping its id — then the item's
+   * settings. A payload omits a setting — or the whole optional `data` — when
+   * its value equals the schema default, so merging into the previous store
+   * would keep the previous locale's value visible. Partial updates still
+   * merge. Either way the `_store` ref changes, which invalidates the memoized
+   * snapshot below. The subscriber emit is queued instead of fired when a
+   * render-phase deferral is active (see `collectDeferredItemUpdates`).
    */
   setData = (update) => {
-    this.data = flattenItemData(update);
+    if ("id" in update && "type" in update) {
+      let { data, type } = update;
+      let schema = this.weaverse.elementRegistry.get(type)?.schema;
+      this._store = {
+        ...generateDataFromSchema(schema),
+        ...data === void 0 ? {} : { data },
+        ...flattenItemData(update)
+      };
+    } else {
+      this.data = flattenItemData(update);
+    }
     if (deferredItemUpdates) {
       deferredItemUpdates.add(this);
     } else {