@delacour/react-native-ui 0.1.0-alpha.20261004035233 → 0.1.0-alpha.20261004043720

package/README.md

@@ -82,7 +82,7 @@ import { IconArrowRight } from "@delacour/react-native-ui/icons/central";
 | --- | --- | --- |
 | Accordion | `@delacour/react-native-ui/accordion` | Selection modes, measured panels, indicators |
 | Badge | `@delacour/react-native-ui/badge` | Variants, colours, sizes, dismiss |
-| BottomSheet | `@delacour/react-native-ui/bottom-sheet` | Detents, keyboard, sticky footer, scrollables, steps, detached, teleported portal |
+| BottomSheet | `@delacour/react-native-ui/bottom-sheet` | Snap points, keyboard, sticky footer, scrollables, steps, detached, teleported portal |
 | Button | `@delacour/react-native-ui/button` | Variants, sizes, icons, loading |
 | Checkbox | `@delacour/react-native-ui/checkbox` | Colours, sizes, indeterminate, groups |
 | Field | `@delacour/react-native-ui/field` | Form layout, grouping, state cascade |

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@delacour/react-native-ui",
-	"version": "0.1.0-alpha.20261004035233",
+	"version": "0.1.0-alpha.20261004043720",
 	"description": "React Native UI components — Uniwind, Reanimated, Gesture Handler",
 	"type": "module",
 	"license": "MIT",
@@ -100,8 +100,8 @@
 	},
 	"peerDependencies": {
 		"@central-icons-react-native/round-outlined-radius-1-stroke-1.5": "^1.1",
-		"@delacour/react-native-bottom-sheet": "0.1.0-alpha.20261004035233",
-		"@delacour/react-native-charts": "0.1.0-alpha.20261004035233",
+		"@delacour/react-native-bottom-sheet": "0.1.0-alpha.20261004043720",
+		"@delacour/react-native-charts": "0.1.0-alpha.20261004043720",
 		"@legendapp/list": ">=3.3",
 		"expo-linear-gradient": ">=15",
 		"expo-router": ">=57",

package/src/components/bottom-sheet/AGENTS.md

@@ -71,7 +71,7 @@ engine's names win everywhere; this skin aliases nothing.
 ## What the engine owns
 
 Everything that is not a class. The open state and the intent queue; the
-height-space geometry and the detents; the handle and content pans and how a
+height-space geometry and the snap points; the handle and content pans and how a
 list shares a finger with them; the keyboard — who owns it, `interactive` /
 `extend` / `fillParent` / `none`, the lift and the restore; the sticky footer's
 line and the safe-area band under it; the teleport portal, the hosts, the
@@ -92,7 +92,7 @@ read those before touching behaviour, because behaviour is not here.
   components applies: the engine is another package.
 - **Where the classes land.** `Content`, `Footer` and `Steps` hand `style` to
   the engine's *measured* inner view, so a class there is height the dynamic
-  detent counts. `ScrollView` puts its content classes on an inner `View`
+  snap point counts. `ScrollView` puts its content classes on an inner `View`
   rather than the content container, so the one style this file writes there —
   the gap above a pinned footer — has a single writer. The three virtualised
   lists have no inner box, so theirs go on `contentContainerClassName`; the
@@ -115,16 +115,16 @@ read those before touching behaviour, because behaviour is not here.
   `fade` and an 8pt slop, for `Badge.CloseButton`'s and `Checkbox`'s reasons.
 - **The root fills in three defaults.** `bottomInset` is `useSafeAreaInsets().bottom`,
   so the engine reserves the home-indicator band and nobody pads for it by
-  hand. `onDetentHaptic` is `Presets.System.selection` and `onCloseHaptic` is
+  hand. `onSnapPointHaptic` is `Presets.System.selection` and `onCloseHaptic` is
   `Presets.System.impactLight` — pulsar's presets are worklets, so they are
   passed as they are; a JS function there is `undefined is not a function` on
   the UI thread. And `useKeyboardAnimationGuard()` runs on mount, the same
   stale-keyboard repair `Screen.Footer` runs. `topInset` stays at the engine's
-  zero, so a `%` detent is the fraction of the window it always was.
+  zero, so a `%` snap point is the fraction of the window it always was.
 - **`Footer.sticky` defaults to `false`**, matching `Screen.Footer`, and this is
   the one engine default the skin overrides. A pinned footer takes
   `padding={BOTTOM_SHEET_FOOTER_PADDING}` through the engine's prop rather
-  than a class, so the padding is inside the box the detent measures; the
+  than a class, so the padding is inside the box the snap point measures; the
   `stickyFooter` slot carries the gutter, the surface and the hairline, and
   the test asserts it carries no vertical padding.
 - **The overlay's opacity is 1**, because `--overlay` carries its own alpha and
@@ -178,7 +178,7 @@ problem it has:
 - nesting a sheet in a sheet — the registry stacks them; `stackBehavior` and
   `dismissAll` are for exactly that
 - `ScrollView` needing `dynamicSizing={false}` and `snapPoints` — a list's
-  content size is the dynamic detent
+  content size is the dynamic snap point
 - lifting `Overlay` and a sticky `Footer` out of the tree as render props —
   every part renders where it is written
 - a `Content` inside a `Container` paying the safe-area band by hand — the

package/src/components/bottom-sheet/bottom-sheet-flat-list.tsx

@@ -37,7 +37,7 @@ export type BottomSheetFlatListProps<ItemT> = HeadlessProps<ItemT> & {
  * A virtualised body.
  *
  * The engine's `FlatList` — the scroll lock, the drag budget and content size
- * as the dynamic detent are all its — with the library's gutter on the content
+ * as the dynamic snap point are all its — with the library's gutter on the content
  * container. A virtualised list has no inner box to put the classes on, so
  * here they go on `contentContainerClassName`; the engine flattens the
  * resulting style to one object before the list measures it.

package/src/components/bottom-sheet/bottom-sheet-footer.tsx

@@ -36,7 +36,7 @@ export type BottomSheetFooterProps = HeadlessProps & {
  * geometry's footer line, which the core proves holds still through a keyboard
  * animation, so its buttons land on the keyboard's top edge without moving;
  * the safe-area band under it is a spacer the geometry owns; and its measured
- * height is what the body reserves and the dynamic detent counts. The
+ * height is what the body reserves and the dynamic snap point counts. The
  * `padding` goes to the engine rather than a class for that reason — it has to
  * be inside the measured box.
  *

package/src/components/bottom-sheet/bottom-sheet-handle.tsx

@@ -25,7 +25,7 @@ export type BottomSheetHandleProps = HeadlessProps & {
  *
  * The engine's handle draws nothing of its own: it owns the pan, measures
  * itself into the sheet's height, and is the adjustable element a screen
- * reader steps through the detents with. This puts the pill inside it, and
+ * reader steps through the snap points with. This puts the pill inside it, and
  * classes on both.
  *
  * Pass children to replace the pill; the row, the pan and the accessibility

package/src/components/bottom-sheet/bottom-sheet-legend-list.tsx

@@ -44,7 +44,7 @@ export type BottomSheetLegendListProps<ItemT> = Omit<AnimatedLegendListProps<Ite
  * Built here rather than in the engine because `@legendapp/list` is this
  * library's optional peer, not the engine's: the engine exports the factory,
  * and this is what the factory is for. The same scroll lock, drag budget and
- * content-size detent as the other three bodies.
+ * content-size snap point as the other three bodies.
  *
  * @example
  * <BottomSheet.LegendList data={rows} keyExtractor={(row) => row.id} renderItem={renderRow} />

package/src/components/bottom-sheet/bottom-sheet-scroll-view.tsx

@@ -36,13 +36,13 @@ export type BottomSheetScrollViewProps = Omit<HeadlessProps, "children"> & {
  * A scrolling body.
  *
  * Use this rather than a plain `ScrollView`: the engine's scrollable and the
- * sheet's pan share a finger — below the highest detent the list is held and
+ * sheet's pan share a finger — below the highest snap point the list is held and
  * the drag moves the sheet, at the highest the list scrolls, and a drag down
  * from the top hands back to the sheet. A React Native `ScrollView` in here has
  * no such arrangement.
  *
  * **It needs no `snapPoints` and no `dynamicSizing={false}`.** The list
- * reports its content size, and that is the dynamic detent: six rows make a
+ * reports its content size, and that is the dynamic snap point: six rows make a
  * short sheet, forty make one capped at `maxDynamicContentSize` that scrolls
  * inside the cap. Explicit `snapPoints` on the root still work, for a height
  * that is a decision rather than a measurement.

package/src/components/bottom-sheet/bottom-sheet.tsx

@@ -38,11 +38,11 @@ export type BottomSheetProps = HeadlessBottomSheetProps;
  * Both run on the UI thread from inside the engine's pan, so they are
  * `Presets.System.*` — themselves worklets — and nothing else: a JS function
  * here would be `undefined is not a function` at the moment a finger crosses a
- * detent. `selection` on a detent because that is what a picker's tick feels
+ * snap point. `selection` on a snap point because that is what a picker's tick feels
  * like, and `impactLight` on a close because letting go of a sheet is a
  * heavier event than passing a stop, but not by much.
  */
-const detentHaptic = Presets.System.selection;
+const snapPointHaptic = Presets.System.selection;
 const closeHaptic = Presets.System.impactLight;
 
 /**
@@ -55,19 +55,19 @@ const closeHaptic = Presets.System.impactLight;
  *   `useSafeAreaInsets()`. The engine reserves that band under the body or the
  *   sticky footer and gives it back to the keyboard as it arrives; a caller
  *   never pads for the home indicator by hand.
- * - **The haptics are on by default.** Pass `onDetentHaptic={undefined}` to
+ * - **The haptics are on by default.** Pass `onSnapPointHaptic={undefined}` to
  *   turn one off, or a worklet of your own to change it.
  * - **The stale-keyboard guard runs on mount.** A sheet mounted while
  *   `KeyboardProvider`'s shared values are pinned open by a keyboard that
  *   vanished without a `will` event would lift for a keyboard that is not
  *   there; `Screen.Footer` runs the same repair for the same reason.
  *
- * `topInset` is left at the engine's zero, so a `%` detent is a fraction of the
+ * `topInset` is left at the engine's zero, so a `%` snap point is a fraction of the
  * whole window — the same fraction it was before this rewrite.
  */
 function BottomSheetRoot({
 	bottomInset,
-	onDetentHaptic = detentHaptic,
+	onSnapPointHaptic = snapPointHaptic,
 	onCloseHaptic = closeHaptic,
 	...props
 }: BottomSheetProps): ReactElement {
@@ -78,7 +78,7 @@ function BottomSheetRoot({
 		<Headless
 			bottomInset={bottomInset ?? insets.bottom}
 			onCloseHaptic={onCloseHaptic}
-			onDetentHaptic={onDetentHaptic}
+			onSnapPointHaptic={onSnapPointHaptic}
 			{...props}
 		/>
 	);

package/src/components/bottom-sheet/bottom-sheet.variants.test.ts

@@ -112,7 +112,7 @@ describe("every token the slots name", () => {
 });
 
 describe("the backdrop indices", () => {
-	test("show the scrim from the first detent and hide it only when closed", () => {
+	test("show the scrim from the first snap point and hide it only when closed", () => {
 		// A modal sheet has no resting state: presented or gone.
 		expect(BOTTOM_SHEET_BACKDROP_INDICES.appearsOnIndex).toBe(0);
 		expect(BOTTOM_SHEET_BACKDROP_INDICES.disappearsOnIndex).toBe(-1);
@@ -198,7 +198,7 @@ describe("bottomSheetVariants slots", () => {
 	test("a pinned footer writes its vertical padding as the engine's prop, never a class", () => {
 		// The engine measures the footer's inner box into the sheet's height, and
 		// padding handed to its `padding` prop lands on that box. A class on the
-		// outer view would be height the detent never counts.
+		// outer view would be height the snap point never counts.
 		expect(SLOTS.stickyFooter()).not.toMatch(/\bp[tby]?-[\d.]+\b/);
 		expect(BOTTOM_SHEET_FOOTER_PADDING).toBeGreaterThan(0);
 	});

package/src/components/bottom-sheet/bottom-sheet.variants.ts

@@ -21,10 +21,10 @@ export const BOTTOM_SHEET_OVERLAY_TOKEN = "overlay";
 export const BOTTOM_SHEET_OVERLAY_OPACITY = 1;
 
 /**
- * The detent indices the scrim appears and disappears on.
+ * The snap point indices the scrim appears and disappears on.
  *
  * A modal sheet has no resting state: it is either presented or gone, so the
- * scrim belongs from the FIRST detent (`0`) and is only absent when the sheet
+ * scrim belongs from the FIRST snap point (`0`) and is only absent when the sheet
  * is closed (`-1`). These are the engine's own defaults too; they are named
  * here so the test that pins them has something to read.
  */
@@ -43,7 +43,7 @@ export const BOTTOM_SHEET_CLOSE_HIT_SLOP = 8;
  * The padding a pinned footer's measured box carries.
  *
  * A number rather than a `p-4`, because it is handed to the engine's `padding`
- * prop: the engine measures the footer's inner box into the dynamic detent,
+ * prop: the engine measures the footer's inner box into the dynamic snap point,
  * and padding written there is counted where a class on the outer view would
  * not be. The horizontal gutter still comes from the `stickyFooter` slot, which
  * is merged after it.