@xaui/native 0.9.1-alpha.9 → 0.9.1-alpha.90

package/dist/create-recipe-BjxSp9_k.d.cts

@@ -1,197 +0,0 @@
-import { ComponentType, ReactNode } from 'react';
-import { ImageSourcePropType, StyleProp, ImageStyle, PressableProps, ViewStyle, TextStyle } from 'react-native';
-import { SharedValue } from 'react-native-reanimated';
-import { g as XAUITheme, X as XAUIColors } from './theme.type-C9bFJKFm.cjs';
-
-/**
- * The props Lucide, Ionicons and `react-native-vector-icons` all accept — the shape
- * `as` is handed. It is a convention rather than an interface anyone published, which is
- * exactly why `Icon` exists: without it every call site computes the two values by hand.
- */
-type IconComponentProps = {
-    size?: number;
-    color?: string;
-};
-type IconProps = {
-    /** An icon component. `size` and `color` are injected into it. */
-    as?: ComponentType<IconComponentProps>;
-    /** A raw `react-native-svg` element, cloned with the resolved size and colour. */
-    children?: ReactNode;
-    /** An image, tinted with the resolved colour. */
-    source?: ImageSourcePropType;
-    /** Overrides what the surrounding slot asked for. */
-    size?: number;
-    /** A raw value (R7), never a token. Overrides the slot's. */
-    color?: string;
-    style?: StyleProp<ImageStyle>;
-};
-/** What a component root publishes so the icons inside it need no props at all. */
-type IconContextValue = {
-    size?: number;
-    color?: string;
-};
-
-/**
- * What the root does under the finger. `scale-highlight` and `scale-ripple` mount their
- * overlay themselves; `scale` mounts none, which is what a root picks when it renders its
- * own `<PressableFeedback.Highlight>` to style it (R1: no prop reaches into another
- * component's insides).
- */
-type FeedbackVariant = 'scale-highlight' | 'scale-ripple' | 'scale' | 'none';
-type AnimationConfig = {
-    scale?: boolean;
-    highlight?: boolean;
-    ripple?: boolean;
-};
-/**
- * `false` and `'disabled'` turn this component's animations off. `'disable-all'` turns
- * them off for its descendants too — a long list kills every row's worklets with one
- * prop instead of threading it down. An object switches them off one at a time.
- */
-type AnimationProp = boolean | 'disabled' | 'disable-all' | AnimationConfig;
-/** `animation` once normalised — what the components actually read. */
-type ResolvedAnimation = {
-    scale: boolean;
-    highlight: boolean;
-    ripple: boolean;
-    /** True when every sub-animation is off: the branch that mounts no worklet at all. */
-    none: boolean;
-    /** Propagated to descendants through context. */
-    disableAll: boolean;
-};
-type PressableFeedbackProps = Omit<PressableProps, 'style' | 'children' | 'disabled'> & {
-    /** Controlled: the root owns the state, because its recipe resolves on it (R5). */
-    isPressed?: boolean;
-    /** R8: `disabled` is not part of the public vocabulary, `isX` is. */
-    isDisabled?: boolean;
-    /**
-     * Merge into the single child instead of rendering a pressable (R12) — **keeping the
-     * feedback**. Swapping this component out for a bare `Slot` would silently drop the
-     * touch feedback of every `asChild` control.
-     */
-    asChild?: boolean;
-    feedbackVariant?: FeedbackVariant;
-    animation?: AnimationProp;
-    style?: StyleProp<ViewStyle>;
-    /**
-     * `Pressable`'s function form is dropped on purpose. It exists to hand the press state
-     * to children; here the root above already owns that state and this publishes it
-     * through context, so the function form would be a second, quieter source of truth.
-     */
-    children?: ReactNode;
-};
-/**
- * A slot's own animation, overriding the blanket one on the root. `false` switches that
- * slot off; the object tunes it. Deliberately two knobs rather than a full timing
- * surface — anything past this is a different animation, and that is a component's job,
- * not a prop's.
- */
-type SlotAnimation = boolean | {
-    /** Milliseconds. Falls back to the shared press timing. */
-    duration?: number;
-    /** How far the overlay goes at full press, 0 to 1. */
-    opacity?: number;
-};
-type FeedbackContext = {
-    isPressed: boolean;
-    animation: ResolvedAnimation;
-    /** Absent on the static branch, where nothing animates and no worklet is mounted. */
-    progress?: SharedValue<number>;
-    /**
-     * Bumped on every press-in. The ripple starts from this rather than from a `useEffect`
-     * on `isPressed`: a one-shot driven by a boolean depends on React re-rendering between
-     * the two touch events, and starting it from the event that carries the coordinates is
-     * both simpler and impossible to miss.
-     */
-    pressCount?: SharedValue<number>;
-    /** Where the finger landed, and how big the root is — the ripple needs both. */
-    origin?: SharedValue<{
-        x: number;
-        y: number;
-    }>;
-    size?: SharedValue<{
-        width: number;
-        height: number;
-    }>;
-};
-
-/**
- * A slot is a view or a text node, and a recipe writes one object per slot, so the two
- * RN style shapes are merged rather than discriminated per slot.
- */
-type SlotStyle = ViewStyle & TextStyle;
-type SlotStyles<Slot extends string> = Partial<Record<Slot, SlotStyle>>;
-/** The roles a variant consumes. The variant names tokens; `paint` says where they land. */
-type VariantRole = 'bg' | 'bgPressed' | 'fg' | 'border';
-/** Token names per role — no colour value ever appears in a recipe. */
-type VariantTokens = Partial<Record<VariantRole, keyof XAUIColors>>;
-/** The same roles resolved: theme colours, or the slices of a raw `color`. */
-type VariantColors = Partial<Record<VariantRole, string>>;
-/**
- * `disabled` is applied last of the three: a control that is both pressed and disabled
- * has to read disabled.
- */
-type StateName = 'focused' | 'pressed' | 'disabled';
-type States = Partial<Record<StateName, boolean>>;
-/** Reads the theme and the variant's resolved colours; returns one style per slot. */
-type StyleFn<Slot extends string> = (theme: XAUITheme, colors: VariantColors) => SlotStyles<Slot>;
-/** Named axes of finite token values — `{ size: { sm: fn, md: fn } }`. */
-type Axes<Slot extends string> = Record<string, Record<string, StyleFn<Slot>>>;
-/** One value per axis, plus the variant. Missing keys fall back to `defaultVariants`. */
-type Selection<Variant extends string, A extends Axes<string>> = {
-    variant?: Variant;
-} & {
-    [Axis in keyof A]?: Extract<keyof A[Axis], string>;
-};
-type CompoundVariant<Slot extends string, Variant extends string, A extends Axes<Slot>> = {
-    when: Selection<Variant, A>;
-    style: StyleFn<Slot>;
-};
-type RecipeConfig<Slot extends string, Variant extends string, A extends Axes<Slot>> = {
-    /** Every slot the component publishes. Slots a recipe never styles resolve to `{}`. */
-    slots: readonly Slot[];
-    base?: StyleFn<Slot>;
-    variantTokens?: Record<Variant, VariantTokens>;
-    /** Where the variant's colours land — written once, and it holds for every variant. */
-    paint?: StyleFn<Slot>;
-    variants?: A;
-    compoundVariants?: ReadonlyArray<CompoundVariant<Slot, Variant, A>>;
-    states?: Partial<Record<StateName, StyleFn<Slot>>>;
-    defaultVariants?: Selection<Variant, A>;
-};
-/** Stable references: the same object for the same tokens, for the app's lifetime. */
-type ResolvedStyles<Slot extends string> = Readonly<Record<Slot, SlotStyle>>;
-/** A selection with `defaultVariants` already folded in, keyed by axis name. */
-type ResolvedSelection = Readonly<Record<string, string | undefined>>;
-
-type ResolveArgs<Variant extends string, A extends Axes<string>> = {
-    theme: XAUITheme;
-    selection?: Selection<Variant, A>;
-    states?: States;
-};
-type TintArgs<Variant extends string, A extends Axes<string>> = ResolveArgs<Variant, A> & {
-    color: string;
-};
-type Recipe<Slot extends string, Variant extends string, A extends Axes<Slot>> = {
-    readonly slots: readonly Slot[];
-    /** The cached pass: stable `StyleSheet` references, keyed by tokens alone. */
-    resolve(args: ResolveArgs<Variant, A>): ResolvedStyles<Slot>;
-    /**
-     * The tint pass: the same functions run again with `color`'s slices in place of the
-     * theme's tokens. Uncached and allocating, and only ever called when `color` is set.
-     */
-    tint(args: TintArgs<Variant, A>): SlotStyles<Slot>;
-};
-/**
- * A component's style, declared once. Resolution splits in two because the two halves
- * have different lifetimes: everything keyed by a finite token is cached forever, and
- * an arbitrary `color` is recomputed per render — which is what keeps the cache bounded
- * by the number of token combinations rather than by the palette users invent.
- *
- *     const styles = buttonRecipe.resolve({ theme, selection: { variant, size }, states })
- *     const tint = color ? buttonRecipe.tint({ theme, color, selection, states }) : undefined
- *     <View style={[styles.root, tint?.root, style]} />
- */
-declare function createRecipe<Slot extends string, Variant extends string, const A extends Axes<Slot>>(config: RecipeConfig<Slot, Variant, A>): Recipe<Slot, Variant, A>;
-
-export { type AnimationConfig as A, type CompoundVariant as C, type FeedbackContext as F, type IconComponentProps as I, type PressableFeedbackProps as P, type ResolvedAnimation as R, type SlotAnimation as S, type TintArgs as T, type VariantColors as V, type IconContextValue as a, type IconProps as b, type AnimationProp as c, type FeedbackVariant as d, createRecipe as e, type Recipe as f, type ResolveArgs as g, type Axes as h, type RecipeConfig as i, type ResolvedSelection as j, type ResolvedStyles as k, type Selection as l, type SlotStyle as m, type SlotStyles as n, type StateName as o, type States as p, type StyleFn as q, type VariantRole as r, type VariantTokens as s };

package/dist/create-recipe-M99yoHrG.d.ts

@@ -1,197 +0,0 @@
-import { ComponentType, ReactNode } from 'react';
-import { ImageSourcePropType, StyleProp, ImageStyle, PressableProps, ViewStyle, TextStyle } from 'react-native';
-import { SharedValue } from 'react-native-reanimated';
-import { g as XAUITheme, X as XAUIColors } from './theme.type-C9bFJKFm.js';
-
-/**
- * The props Lucide, Ionicons and `react-native-vector-icons` all accept — the shape
- * `as` is handed. It is a convention rather than an interface anyone published, which is
- * exactly why `Icon` exists: without it every call site computes the two values by hand.
- */
-type IconComponentProps = {
-    size?: number;
-    color?: string;
-};
-type IconProps = {
-    /** An icon component. `size` and `color` are injected into it. */
-    as?: ComponentType<IconComponentProps>;
-    /** A raw `react-native-svg` element, cloned with the resolved size and colour. */
-    children?: ReactNode;
-    /** An image, tinted with the resolved colour. */
-    source?: ImageSourcePropType;
-    /** Overrides what the surrounding slot asked for. */
-    size?: number;
-    /** A raw value (R7), never a token. Overrides the slot's. */
-    color?: string;
-    style?: StyleProp<ImageStyle>;
-};
-/** What a component root publishes so the icons inside it need no props at all. */
-type IconContextValue = {
-    size?: number;
-    color?: string;
-};
-
-/**
- * What the root does under the finger. `scale-highlight` and `scale-ripple` mount their
- * overlay themselves; `scale` mounts none, which is what a root picks when it renders its
- * own `<PressableFeedback.Highlight>` to style it (R1: no prop reaches into another
- * component's insides).
- */
-type FeedbackVariant = 'scale-highlight' | 'scale-ripple' | 'scale' | 'none';
-type AnimationConfig = {
-    scale?: boolean;
-    highlight?: boolean;
-    ripple?: boolean;
-};
-/**
- * `false` and `'disabled'` turn this component's animations off. `'disable-all'` turns
- * them off for its descendants too — a long list kills every row's worklets with one
- * prop instead of threading it down. An object switches them off one at a time.
- */
-type AnimationProp = boolean | 'disabled' | 'disable-all' | AnimationConfig;
-/** `animation` once normalised — what the components actually read. */
-type ResolvedAnimation = {
-    scale: boolean;
-    highlight: boolean;
-    ripple: boolean;
-    /** True when every sub-animation is off: the branch that mounts no worklet at all. */
-    none: boolean;
-    /** Propagated to descendants through context. */
-    disableAll: boolean;
-};
-type PressableFeedbackProps = Omit<PressableProps, 'style' | 'children' | 'disabled'> & {
-    /** Controlled: the root owns the state, because its recipe resolves on it (R5). */
-    isPressed?: boolean;
-    /** R8: `disabled` is not part of the public vocabulary, `isX` is. */
-    isDisabled?: boolean;
-    /**
-     * Merge into the single child instead of rendering a pressable (R12) — **keeping the
-     * feedback**. Swapping this component out for a bare `Slot` would silently drop the
-     * touch feedback of every `asChild` control.
-     */
-    asChild?: boolean;
-    feedbackVariant?: FeedbackVariant;
-    animation?: AnimationProp;
-    style?: StyleProp<ViewStyle>;
-    /**
-     * `Pressable`'s function form is dropped on purpose. It exists to hand the press state
-     * to children; here the root above already owns that state and this publishes it
-     * through context, so the function form would be a second, quieter source of truth.
-     */
-    children?: ReactNode;
-};
-/**
- * A slot's own animation, overriding the blanket one on the root. `false` switches that
- * slot off; the object tunes it. Deliberately two knobs rather than a full timing
- * surface — anything past this is a different animation, and that is a component's job,
- * not a prop's.
- */
-type SlotAnimation = boolean | {
-    /** Milliseconds. Falls back to the shared press timing. */
-    duration?: number;
-    /** How far the overlay goes at full press, 0 to 1. */
-    opacity?: number;
-};
-type FeedbackContext = {
-    isPressed: boolean;
-    animation: ResolvedAnimation;
-    /** Absent on the static branch, where nothing animates and no worklet is mounted. */
-    progress?: SharedValue<number>;
-    /**
-     * Bumped on every press-in. The ripple starts from this rather than from a `useEffect`
-     * on `isPressed`: a one-shot driven by a boolean depends on React re-rendering between
-     * the two touch events, and starting it from the event that carries the coordinates is
-     * both simpler and impossible to miss.
-     */
-    pressCount?: SharedValue<number>;
-    /** Where the finger landed, and how big the root is — the ripple needs both. */
-    origin?: SharedValue<{
-        x: number;
-        y: number;
-    }>;
-    size?: SharedValue<{
-        width: number;
-        height: number;
-    }>;
-};
-
-/**
- * A slot is a view or a text node, and a recipe writes one object per slot, so the two
- * RN style shapes are merged rather than discriminated per slot.
- */
-type SlotStyle = ViewStyle & TextStyle;
-type SlotStyles<Slot extends string> = Partial<Record<Slot, SlotStyle>>;
-/** The roles a variant consumes. The variant names tokens; `paint` says where they land. */
-type VariantRole = 'bg' | 'bgPressed' | 'fg' | 'border';
-/** Token names per role — no colour value ever appears in a recipe. */
-type VariantTokens = Partial<Record<VariantRole, keyof XAUIColors>>;
-/** The same roles resolved: theme colours, or the slices of a raw `color`. */
-type VariantColors = Partial<Record<VariantRole, string>>;
-/**
- * `disabled` is applied last of the three: a control that is both pressed and disabled
- * has to read disabled.
- */
-type StateName = 'focused' | 'pressed' | 'disabled';
-type States = Partial<Record<StateName, boolean>>;
-/** Reads the theme and the variant's resolved colours; returns one style per slot. */
-type StyleFn<Slot extends string> = (theme: XAUITheme, colors: VariantColors) => SlotStyles<Slot>;
-/** Named axes of finite token values — `{ size: { sm: fn, md: fn } }`. */
-type Axes<Slot extends string> = Record<string, Record<string, StyleFn<Slot>>>;
-/** One value per axis, plus the variant. Missing keys fall back to `defaultVariants`. */
-type Selection<Variant extends string, A extends Axes<string>> = {
-    variant?: Variant;
-} & {
-    [Axis in keyof A]?: Extract<keyof A[Axis], string>;
-};
-type CompoundVariant<Slot extends string, Variant extends string, A extends Axes<Slot>> = {
-    when: Selection<Variant, A>;
-    style: StyleFn<Slot>;
-};
-type RecipeConfig<Slot extends string, Variant extends string, A extends Axes<Slot>> = {
-    /** Every slot the component publishes. Slots a recipe never styles resolve to `{}`. */
-    slots: readonly Slot[];
-    base?: StyleFn<Slot>;
-    variantTokens?: Record<Variant, VariantTokens>;
-    /** Where the variant's colours land — written once, and it holds for every variant. */
-    paint?: StyleFn<Slot>;
-    variants?: A;
-    compoundVariants?: ReadonlyArray<CompoundVariant<Slot, Variant, A>>;
-    states?: Partial<Record<StateName, StyleFn<Slot>>>;
-    defaultVariants?: Selection<Variant, A>;
-};
-/** Stable references: the same object for the same tokens, for the app's lifetime. */
-type ResolvedStyles<Slot extends string> = Readonly<Record<Slot, SlotStyle>>;
-/** A selection with `defaultVariants` already folded in, keyed by axis name. */
-type ResolvedSelection = Readonly<Record<string, string | undefined>>;
-
-type ResolveArgs<Variant extends string, A extends Axes<string>> = {
-    theme: XAUITheme;
-    selection?: Selection<Variant, A>;
-    states?: States;
-};
-type TintArgs<Variant extends string, A extends Axes<string>> = ResolveArgs<Variant, A> & {
-    color: string;
-};
-type Recipe<Slot extends string, Variant extends string, A extends Axes<Slot>> = {
-    readonly slots: readonly Slot[];
-    /** The cached pass: stable `StyleSheet` references, keyed by tokens alone. */
-    resolve(args: ResolveArgs<Variant, A>): ResolvedStyles<Slot>;
-    /**
-     * The tint pass: the same functions run again with `color`'s slices in place of the
-     * theme's tokens. Uncached and allocating, and only ever called when `color` is set.
-     */
-    tint(args: TintArgs<Variant, A>): SlotStyles<Slot>;
-};
-/**
- * A component's style, declared once. Resolution splits in two because the two halves
- * have different lifetimes: everything keyed by a finite token is cached forever, and
- * an arbitrary `color` is recomputed per render — which is what keeps the cache bounded
- * by the number of token combinations rather than by the palette users invent.
- *
- *     const styles = buttonRecipe.resolve({ theme, selection: { variant, size }, states })
- *     const tint = color ? buttonRecipe.tint({ theme, color, selection, states }) : undefined
- *     <View style={[styles.root, tint?.root, style]} />
- */
-declare function createRecipe<Slot extends string, Variant extends string, const A extends Axes<Slot>>(config: RecipeConfig<Slot, Variant, A>): Recipe<Slot, Variant, A>;
-
-export { type AnimationConfig as A, type CompoundVariant as C, type FeedbackContext as F, type IconComponentProps as I, type PressableFeedbackProps as P, type ResolvedAnimation as R, type SlotAnimation as S, type TintArgs as T, type VariantColors as V, type IconContextValue as a, type IconProps as b, type AnimationProp as c, type FeedbackVariant as d, createRecipe as e, type Recipe as f, type ResolveArgs as g, type Axes as h, type RecipeConfig as i, type ResolvedSelection as j, type ResolvedStyles as k, type Selection as l, type SlotStyle as m, type SlotStyles as n, type StateName as o, type States as p, type StyleFn as q, type VariantRole as r, type VariantTokens as s };