@symbiote-native/components 3.1.0 → 3.1.1

package/README.md

@@ -20,17 +20,19 @@ supplies only the third:
 
 1. **Logic — `src/state/*.ts`.** A pure reducer `(state, action) => state`, a
    `createInitial*State` factory, and pure predicates. Zero framework, zero render —
-   `switchReducer` / `shouldSnapBack` / `valueFromChange` for `Switch`, `modalReducer` for `Modal`,
-   the `virtualized-list` windowing math for the list family.
+   `modalReducer` for `Modal`, `shouldSnapBack` / `valueFromChange` for `Pressable`'s press
+   machine, the `virtualized-list` windowing math for the list family.
 2. **View — `src/view/render-*.ts`.** A pure function `render*(viewState, platform) => Descriptor`.
    State and visuals enter **only through arguments**; out comes a tree of `Descriptor` nodes
    (`{ type, props, children, key }`, built with `el()` / `txt()`) over the intrinsic primitives
-   (`symbiote-view`, `symbiote-switch`, …). No framework, no state, no events.
+   (`symbiote-view`, `symbiote-scroll-view`, …). No framework, no state, no events.
 3. **Lifecycle — the adapter.** React wires the reducer through `useReducer`/`useLayoutEffect` and
    bridges the `Descriptor` to `React.createElement`; Vue wires it through `ref`/`watch` and
    bridges to `h()`. This is the ONLY part a new adapter has to write.
 
-`Switch` is the canonical reference for a full three-layer component.
+`Modal` is the canonical reference for a full three-layer component. `Switch` used to be — its
+`render*` function is gone now that the painting moved to the `switch` tag's own host behavior
+(see "Host behaviors" below), so only its reducer and prop type still live at this layer.
 
 ### Install
 
@@ -45,28 +47,25 @@ npm install @symbiote-native/components
 ## Usage
 
 Nearly every consumer reaches this package **through an adapter**, not directly — an app imports
-`Switch` from `@symbiote-native/react` (or `@symbiote-native/vue`), and that adapter re-exports the prop
+`Modal` from `@symbiote-native/react` (or `@symbiote-native/vue`), and that adapter re-exports the prop
 types and wires the reducer/render pair from here. Calling the render function directly is what an
 adapter itself does, to build its lifecycle wrapper:
 
 ```ts
 import {
-  renderSwitch,
-  createInitialSwitchState,
-  switchReducer,
+  renderModal,
+  createInitialModalState,
+  modalReducer,
 } from '@symbiote-native/components';
 
 // inside an adapter's own hook/composable:
-const state = createInitialSwitchState();
-const next = switchReducer(state, { type: 'native-reported', value: true });
-const descriptor = renderSwitch(
-  { value: true, disabled: false, passthrough: { onChange, ref } },
-  {
-    trackColorProps: (value, trackColor) => ({
-      /* platform-specific prop names */
-    }),
-  },
-);
+const state = createInitialModalState(visible);
+const next = modalReducer(state, { type: visible ? 'show' : 'hide' });
+const descriptor = renderModal({
+  visible,
+  transparent: false,
+  passthrough: { onDismiss, onRequestClose, ref },
+});
 // descriptor is then handed to the adapter's own descriptorToReact / descriptorToVue bridge
 ```
 

package/build/behaviors/button.js

@@ -111,7 +111,7 @@
 // since 2026-09-09, in the same commit that deleted the five wrappers, which is what makes it safe:
 // while a wrapper still built its own view and text under this tag, registering would have given
 // every Button a second copy of the subtree.
-import { addDerivedNode, appendChild, createElement, createRawText, markPropsDirty, Platform, registerHostBehavior, requestCommitFor, setProp, } from '@symbiote-native/engine';
+import { addDerivedNode, appendChild, createElement, createRawText, markPropsDirty, Platform, registerHostBehavior, requestCommitFor, } from '@symbiote-native/engine';
 import { descriptorFor } from '../component-names';
 import { resolveButtonDisabled } from '../view/render-button.js';
 import { booleanOr, createPressBehavior, } from './pressable.js';

package/build/behaviors/scroll-view/shared.js

@@ -81,7 +81,7 @@
 // The slot's fold is assigned to the node inside `buildStructure`, not declared on the behavior:
 // `IHostBehavior.foldPayload` is the OWNER's, wired by `attachHostBehavior`, and a behavior that
 // builds a node owns what that node carries.
-import { appendChild, appListenerFor, createElement, dlog, registerHostBehavior, setBehaviorListener, setEventListener, setProp, } from '@symbiote-native/engine';
+import { appendChild, appListenerFor, createElement, dlog, registerHostBehavior, setBehaviorListener, setEventListener, } from '@symbiote-native/engine';
 import { descriptorFor } from '../../component-names';
 import { didContentSizeChange, readLayoutDimension, } from '../../view/render-scroll-view.js';
 import { installResponderPredicates, RESPONDER_OWNED_LISTENERS, } from './responder.js';
@@ -151,8 +151,7 @@ export const REFRESH_CONTROL = descriptorFor('refresh-control').component;
 // `core/engine/cpp/tests/js/scroll-content-payload.itest.ts`.
 // `rowStyle` USED TO BE A PARAMETER HERE and is not one any more: the content node's row direction
 // is decided in the engine from that node's OWN tag (`horizontal-scroll-content`), so this builder
-// no longer needs to know the axis to build it. `scrollBehavior` still derives `horizontal` from the
-// row style for the things that DO still need it in JS.
+// no longer needs to know the axis to build it.
 function buildContent(contentIntrinsic) {
     return (node) => {
         const descriptor = descriptorFor(contentIntrinsic);
@@ -233,9 +232,6 @@ function syncOwnedListener(owner, name, wired) {
         syncOwnerLayout(owner);
 }
 function scrollBehavior(contentIntrinsic, rowStyle, platform) {
-    // The row style is the horizontal tag's constant and nothing else carries it, so it IS the axis —
-    // deriving keeps the two from ever disagreeing about which behavior this is.
-    const horizontal = rowStyle !== undefined;
     return {
         // `scroll` and `layout` are owned for the collision reason rather than because the behavior
         // consumes them: RN's ScrollView installs `_handleScroll` and `_handleLayout` on the native

package/build/bootstrap/index.d.ts

@@ -2,6 +2,7 @@ import { type IColorValue, type IDeviceEventSource, type INativeViewConfigSource
 export type IBootstrapHostOptions = {
     colorProcessor?: (value: IColorValue) => unknown;
     imageSourceResolver?: (source: unknown) => unknown;
+    assetSourceResolver?: (source: unknown) => unknown;
     deviceEventSource?: IDeviceEventSource;
     nativeViewConfigSource?: INativeViewConfigSource;
     debug?: boolean;

package/build/bootstrap/index.js

@@ -5,7 +5,7 @@
 // export): react-native's own source is Flow syntax Vitest's transform can't parse, so anything
 // importing it directly must stay unreachable from the tested main index.ts.
 import { processColor, DeviceEventEmitter, Image, } from 'react-native';
-import { installBackHandler, setColorProcessor, setDeviceEventSource, setImageSourceResolver, setNativeViewConfigSource, } from '@symbiote-native/engine';
+import { setAssetSourceResolver, installBackHandler, setColorProcessor, setDeviceEventSource, setImageSourceResolver, setNativeViewConfigSource, } from '@symbiote-native/engine';
 // @ts-expect-error react-native ships no types for this internal path (plain .js) - the
 // try/catch below is what actually proves the shape, not TS.
 import * as ReactNativeViewConfigRegistry from 'react-native/Libraries/Renderer/shims/ReactNativeViewConfigRegistry';
@@ -37,6 +37,7 @@ export function bootstrapHost(options = {}) {
     globalThis.__SYMBIOTE_DEBUG__ = options.debug ?? process.env.DEBUG === '1';
     setColorProcessor(options.colorProcessor ?? defaultColorProcessor);
     setImageSourceResolver(options.imageSourceResolver ?? defaultImageSourceResolver);
+    setAssetSourceResolver(options.assetSourceResolver ?? defaultImageSourceResolver);
     setDeviceEventSource(options.deviceEventSource ?? DeviceEventEmitter);
     // After the event source: the back button subscribes through it (see installBackHandler).
     installBackHandler();

package/build/scroll-view-commands.js

@@ -1,9 +1,9 @@
-// ScrollView: the imperative + style-routing module (framework-agnostic, no 3-layer split:
-// ScrollView has no state machine). The imperative handle, the layout/visual style split for
-// the Android RefreshControl wrap, the scroll-event guard/forwarder, and the native sticky
-// scroll-attach are all platform- and framework-invariant, so they live here. The adapter
-// supplies the lifecycle (the node getter, the effect) and re-exports these.
-import { attachNativeEvent, dlog, flattenStyle, isSymbioteEvent, } from '@symbiote-native/engine';
+// ScrollView: the imperative + event-routing module (framework-agnostic, no 3-layer split:
+// ScrollView has no state machine). The imperative handle, the scroll-event guard/forwarder, and
+// the native sticky scroll-attach are platform- and framework-invariant, so they live here. The
+// Android RefreshControl wrap's style split moved out — see the note below. The adapter supplies
+// the lifecycle (the node getter, the effect) and re-exports these.
+import { attachNativeEvent, dlog, isSymbioteEvent, } from '@symbiote-native/engine';
 // THE ANDROID WRAP SPLIT LEFT THIS FILE ON 2026-09-18, and with it the last copy of RN's
 // `splitLayoutProps` key partition. Both halves are `SymbioteFabricProps.cpp` now
 // (`splitScrollViewStyle`, `foldRefreshWrapperProps`), reached off the tag and the tree rather than

package/build/view/render-button.js

@@ -11,15 +11,6 @@
 // What is NOT here, because a layer below already does it: the `aria-*` -> `accessibilityState`
 // fold RN performs in `Button.js:326-331`. The engine folds those for every node
 // (`core/engine/src/accessibility-props.ts`), so repeating it here would fold twice.
-import { Platform } from '@symbiote-native/engine';
-// Button.js:394-437, one constant per literal so a value cannot drift silently. The LABEL's seven
-// went with `resolveButtonTextStyle` on 2026-09-18 — they live in `SymbioteFabricProps.cpp` beside
-// the rule that reads them and are deliberately not duplicated here.
-const ANDROID_BUTTON_BLUE = '#2196F3';
-const ANDROID_DISABLED_BACKGROUND = '#dfdfdf';
-const ANDROID_ELEVATION = 4;
-const ANDROID_DISABLED_ELEVATION = 0;
-const ANDROID_BORDER_RADIUS = 2;
 // `BUTTON_ACCESSIBILITY_ROLE` and `resolveButtonImportantForAccessibility` WERE HERE and are gone
 // (2026-09-18). Both are `foldButtonProps` in `SymbioteFabricProps.cpp` now, and neither had a
 // caller left afterwards — only its own unit test, which is the shape this project calls a mirror:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@symbiote-native/components",
-  "version": "3.1.0",
+  "version": "3.1.1",
   "description": "Framework-agnostic component logic (state machines + render functions) for SymbioteNative — written once, inherited by every adapter (React, Vue, Angular, ...).",
   "license": "MIT",
   "repository": {
@@ -59,11 +59,11 @@
   },
   "peerDependencies": {
     "react-native": ">=0.86",
-    "@symbiote-native/engine": "^1.2.0"
+    "@symbiote-native/engine": "^1.3.0"
   },
   "devDependencies": {
     "@types/node": "^26.0.0",
-    "@symbiote-native/engine": "1.2.0"
+    "@symbiote-native/engine": "1.3.0"
   },
   "scripts": {
     "typecheck": "tsc --build",