Skip to content

INTEGRATIONS.md

Latest commit

 

History

History
66 lines (54 loc) · 2.22 KB

INTEGRATIONS.md

File metadata and controls

66 lines (54 loc) · 2.22 KB
Raw

Integrations

The documentation site runs these integrations with the published packages. They are development dependencies of the website only; Pull to Refresh keeps zero runtime dependencies beyond React peers.

Swipe Actions

Place swipeable rows inside PullToRefresh.Content. Pull to Refresh waits through its movement slop and rejects horizontal intent, leaving the row primitive free to claim the gesture.

<PullToRefresh.Root onRefresh={refresh}>
  <PullToRefresh.Content>
    <SwipeActions.Group>
      {items.map((item) => (
        <SwipeActions.Root key={item.id}>
          <SwipeActions.Trailing>{/* actions */}</SwipeActions.Trailing>
          <SwipeActions.Content>{/* row */}</SwipeActions.Content>
        </SwipeActions.Root>
      ))}
    </SwipeActions.Group>
  </PullToRefresh.Content>
</PullToRefresh.Root>

Ownership is explicit:

  • horizontal intent → Swipe Actions;
  • ordinary vertical movement → scroll container;
  • downward intent at the top → Pull to Refresh.

Spring Bottom Sheet

Keep the sheet handle outside the feed and pass the feed’s actual scrolling element explicitly:

<Sheet.Content>
  <Sheet.Handle />
  <PullToRefresh.Root
    ref={scrollRef}
    className="sheet-scroll"
    onRefresh={refresh}
    onPointerDown={(event) => event.stopPropagation()}
    scrollContainer={scrollRef}
  >
    <PullToRefresh.Content>{/* feed */}</PullToRefresh.Content>
  </PullToRefresh.Root>
</Sheet.Content>

Make the root itself scrollable. Avoid placing it inside a competing scroll surface when the root is expected to receive the gesture; pass the intended owner explicitly when the layout is ambiguous.

Stop pointer-down propagation from the feed when the sheet handle is the only surface that should drag the sheet. This leaves the browser default untouched, so ordinary list scrolling still works, while preventing the sheet and PTR from racing to capture the same downward gesture at the top boundary.

The documentation proof uses the published v5 package. Desktop automation verifies that the sheet opens, scrolls the dedicated root, and closes. Combined drag behavior was not tested on physical iOS or Android devices for 1.0.0; desktop automation is not presented as physical-device verification.