@symbiote-native/solid 1.0.0 → 3.0.0

package/build/components/touchable-native-feedback/index.jsx

@@ -1,68 +0,0 @@
-// TouchableNativeFeedback — Android's ripple / state-drawable touchable, built on Pressable like
-// the rest of the family. RN clones its child into an RCTView carrying the native ripple props;
-// we nest the child under a feedback view that carries them, inside a Pressable that owns the
-// press wiring. `nativeBackgroundAndroid` / `nativeForegroundAndroid` are read by Android's
-// ReactViewManager; on iOS they are inert props, so the component still renders its child with
-// working press wiring — exactly what React's and Vue's do.
-//
-// EVERYTHING NON-LIFECYCLE IS SHARED. The static factories (selectableBackground,
-// selectableBackgroundBorderless, rippleBackground), the platform gate (canUseNativeForeground)
-// and the background→native-prop mapping (backgroundProps) all live in
-// @symbiote-native/components; this file only attaches them to the component value and nests the
-// feedback view. Press timing is Pressable's, which is the shared state machine.
-//
-// The feedback carrier is a raw `symbiote-view`, not the `View` component — the same choice
-// Pressable already makes for its android_ripple wrapper. It carries native props and nothing
-// else: no accessibility surface, no class, no ref, so View's aria fold and nativeID resolution
-// would be pure overhead. The committed node is `RCTView` either way.
-//
-// NOTHING here destructures `props`. A Solid component body runs ONCE, so a destructure would
-// freeze the background at its mount-time value; every read below sits inside an accessor.
-import { splitProps } from 'solid-js';
-import { backgroundProps, canUseNativeForeground, rippleBackground, selectableBackground, selectableBackgroundBorderless, } from '@symbiote-native/components';
-import { dlog } from '@symbiote-native/engine';
-import { withStableKeys } from '../../utils/stable-keys.js';
-import { TouchablePressable as Pressable, } from '../pressable.jsx';
-function TouchableNativeFeedbackImpl(props) {
-    const [local, rest] = splitProps(props, [
-        'background',
-        'useForeground',
-        'children',
-    ]);
-    // ONE bag, and it goes through withStableKeys. backgroundProps returns a DIFFERENT single key
-    // per branch (nativeForegroundAndroid vs nativeBackgroundAndroid), and Solid's `spread` walks
-    // only the current key set with no removal pass — so flipping `useForeground` on an Android
-    // host would leave the abandoned key painting its old drawable forever. Widening restores what
-    // React and Vue get from their reconcilers: the vanished key arrives as `undefined`, which
-    // routeProp treats as a delete, and `spread` still does the actual diffing
-    // (.claude/rules/solid-descriptor-bridge.md §1).
-    const feedbackProps = withStableKeys(() => {
-        // RN never leaves a TouchableNativeFeedback without feedback: a missing background defaults
-        // to SelectableBackground().
-        const resolved = local.background ?? selectableBackground();
-        const useForeground = local.useForeground === true;
-        dlog(`TouchableNativeFeedback render ${resolved.type} useForeground ${useForeground}`);
-        // The no-op seam: RN silently routes a requested foreground back to the background slot off
-        // Android / below API 23, and a missing ripple on device looks like a broken component.
-        if (useForeground && !canUseNativeForeground()) {
-            dlog('TouchableNativeFeedback useForeground ignored: no native foreground here');
-        }
-        return backgroundProps(resolved, useForeground);
-    });
-    // Two single spreads, never spread-then-override: `mergeProps` (which the compiler uses for a
-    // spread followed by an explicit prop) keeps the FIRST non-undefined value, so an explicit
-    // `undefined` after a spread silently loses — the opposite of React's JSX spread
-    // (.claude/rules/solid-descriptor-bridge.md §6). `rest` and `feedbackProps()` are each the sole
-    // source for their element, so there is nothing to merge.
-    return (<Pressable {...rest}>
-      <symbiote-view {...feedbackProps()}>{local.children}</symbiote-view>
-    </Pressable>);
-}
-// The statics ride on the component value so callers reach TouchableNativeFeedback.Ripple(…)
-// exactly like RN. They are the shared functions themselves, not wrappers.
-export const TouchableNativeFeedback = Object.assign(TouchableNativeFeedbackImpl, {
-    SelectableBackground: selectableBackground,
-    SelectableBackgroundBorderless: selectableBackgroundBorderless,
-    Ripple: rippleBackground,
-    canUseNativeForeground,
-});

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>);
-}

package/build/state-style.d.ts

@@ -1 +0,0 @@
-export { resolveStateStyle, type IPressStateArgument, type IResolvedStateStyle, } from '@symbiote-native/components/state-style';

package/build/state-style.js

@@ -1,13 +0,0 @@
-// Re-export only. The implementation is shared (`@symbiote-native/components`) because two adapters
-// had written byte-identical copies; this file exists so the code a transform EMITS keeps importing
-// from the adapter package the app already depends on, rather than reaching past it.
-//
-// Imported from the SUBPATH, not the barrel: every adapter barrel re-exports
-// `@symbiote-native/components` wholesale, so a name on that barrel silently becomes public API on
-// all five — which is how a transform internal nearly shipped as a supported export.
-//
-// Present on every adapter, including those with no lowering transform yet: a per-framework subpath
-// that four of five declare is exactly the silent gap `tests/package-subpath-parity.test.ts` exists
-// to catch, and the file costs a re-export. Deliberately NOT on the public barrel — the emitted
-// code names it, app code does not.
-export { resolveStateStyle, } from '@symbiote-native/components/state-style';