@timber-js/app 0.2.0-alpha.170 → 0.2.0-alpha.172

package/src/client/child-segment-context.ts

@@ -1,40 +0,0 @@
-/**
- * ChildSegmentContext — delivers child segment content to ChildSegmentOutlet.
- *
- * Each layout receives a stable <ChildSegmentOutlet /> client reference as
- * its `children` prop instead of varying server content. The actual child
- * content (page or inner layout) is provided via this context from a
- * ChildSegmentProvider placed ABOVE the layout in the element tree.
- *
- * This structural separation is what makes layout cache.component hits
- * possible: the cached layout payload contains a deterministic client
- * reference as children, not the varying inner content that changes per
- * route. Same pattern as Next.js LayoutRouter.
- *
- * SINGLETON GUARANTEE: Uses globalThis + Symbol.for — same pattern as
- * SegmentUpdateContext. The RSC client bundler can duplicate this module
- * across chunks; globalThis guarantees a single context instance.
- *
- * See design/45-cache-lifetimes.md §Layout Propagation.
- */
-
-'use client';
-
-import React, { type ReactNode } from 'react';
-
-const CTX_KEY = Symbol.for('__timber_child_segment_ctx');
-
-function getOrCreateContext(): React.Context<ReactNode> {
-  const existing = (globalThis as Record<symbol, unknown>)[CTX_KEY] as
-    | React.Context<ReactNode>
-    | undefined;
-  if (existing !== undefined) return existing;
-  if (typeof React.createContext === 'function') {
-    const ctx = React.createContext<ReactNode>(null);
-    (globalThis as Record<symbol, unknown>)[CTX_KEY] = ctx;
-    return ctx;
-  }
-  return undefined as unknown as React.Context<ReactNode>;
-}
-
-export const ChildSegmentContext = getOrCreateContext();

package/src/client/child-segment-outlet.tsx

@@ -1,25 +0,0 @@
-/**
- * ChildSegmentOutlet — renders child segment content from context.
- *
- * Passed as `children` to every layout component, replacing the previous
- * pattern of passing rendered server content directly. The layout receives
- * a stable client reference (this component), and the actual child content
- * is delivered via ChildSegmentContext from a provider above the layout.
- *
- * This makes layout cache.component hits possible: the cached layout
- * payload contains this deterministic client reference, not varying
- * server content. On cache hit, the revived payload contains the layout
- * shell + this outlet; the provider above supplies the current request's
- * child content.
- *
- * See design/45-cache-lifetimes.md §Layout Propagation.
- */
-
-'use client';
-
-import { useContext } from 'react';
-import { ChildSegmentContext } from './child-segment-context.js';
-
-export function ChildSegmentOutlet() {
-  return useContext(ChildSegmentContext);
-}

package/src/client/child-segment-provider.tsx

@@ -1,27 +0,0 @@
-/**
- * ChildSegmentProvider — wraps a layout to provide child segment content.
- *
- * Placed above the layout in the element tree so that ChildSegmentOutlet
- * (inside the layout's `children`) can read the actual child content.
- *
- * Tree structure:
- *   ChildSegmentProvider(childContent=innerElement)
- *     └── Layout(children=<ChildSegmentOutlet />)
- *          └── ChildSegmentOutlet → reads context → innerElement
- *
- * See design/45-cache-lifetimes.md §Layout Propagation.
- */
-
-'use client';
-
-import { createElement, type ReactNode } from 'react';
-import { ChildSegmentContext } from './child-segment-context.js';
-
-interface ChildSegmentProviderProps {
-  childContent: ReactNode;
-  children: ReactNode;
-}
-
-export function ChildSegmentProvider({ childContent, children }: ChildSegmentProviderProps) {
-  return createElement(ChildSegmentContext.Provider, { value: childContent }, children);
-}