@symbiote-native/solid 0.1.0 → 2.0.0

package/build/components/view.jsx

@@ -1,49 +0,0 @@
-// View — the Solid host primitive, and the file that fixes the children/ref idiom every other
-// Solid component will copy.
-//
-// WHY THIS IS REAL JSX AND NOT A HAND-BUILT NODE. `symbiote-view` takes a live subtree of the
-// user's components, and reducing that subtree to primitives IS Solid's reconciler. So the only
-// two moving parts are (a) forwarding a prop bag onto one host element and (b) handing the
-// children accessor to the renderer's `insert` — precisely what compiled JSX emits
-// (`spread(el, mergeProps(bag), true)` + `insert(el, () => props.children)`, verified against
-// babel-preset-solid's output). Writing those calls by hand would be the compiler's job done
-// worse, and this is the file a Solid author reads first.
-//
-// There is NO renderView() in @symbiote-native/components, and there must not be
-// (.claude/rules/component-render-fn-boundary.md). A render fn moves to core only when every
-// input is a framework-agnostic VALUE; `children` is a live framework subtree that flows through
-// the reconciler and is never converted back into a Descriptor. So descriptorToSolid has nothing
-// to do here — View builds its host element directly, exactly as React's and Vue's do.
-//
-// NOTHING here destructures `props` at setup. Solid props are getters and a component body runs
-// ONCE; splitProps is the idiomatic split that keeps the rest reactive, and every read of the
-// remaining props happens inside the bag accessor, which `spread` re-runs as a render effect.
-import { splitProps } from 'solid-js';
-import { resolveAccessibilityProps, } from '@symbiote-native/components';
-import { applyHostRef } from '../utils/host-ref.js';
-import { withStableKeys } from '../utils/stable-keys.js';
-export function View(props) {
-    // `children` and `ref` are pulled out rather than left to ride in the bag. Both are skipped by
-    // spreadExpression's prop loop anyway, but leaving them in would make the bag accessor depend on
-    // the children subtree (recomputing every prop when only a child changed) and would put `ref`
-    // behind spread's own ref effect, which re-runs — and so re-calls the caller's ref — on EVERY
-    // prop change. React calls a ref once per attach; this keeps that contract.
-    const [local, rest] = splitProps(props, ['children', 'ref', 'id']);
-    // RN's modern `id` is a W3C-named alias for `nativeID`: View.js copies it over
-    // (`processedProps.nativeID = id`), so `id` wins when both are set. Folded here, with the raw
-    // `id` key dropped so it never reaches Fabric — every non-function prop otherwise passes
-    // through to the slot untouched. `nativeID` is emitted UNCONDITIONALLY (undefined when neither
-    // is set) rather than conditionally like React's resolveId: a key that appears and disappears
-    // between runs is the exact hazard withStableKeys exists for, and not creating it is cheaper
-    // than widening it back.
-    const bag = withStableKeys(() => ({
-        ...resolveAccessibilityProps(rest),
-        nativeID: local.id ?? rest.nativeID,
-    }));
-    const attachRef = (node) => {
-        applyHostRef(local.ref, node);
-    };
-    return (<symbiote-view ref={attachRef} {...bag()}>
-      {local.children}
-    </symbiote-view>);
-}