sk-pull-to-refresh

What problem does it solve?

It eliminates the need to hand-wire pull-to-refresh behavior across mobile protected screens, ensuring refresh triggers correctly and doesn’t interfere with inner scroll containers.

Core Features & Use Cases

• Shell-wide mobile pull-to-refresh default: <PullToRefreshShell> mounts once in DashboardShell and uses router.refresh() as the canonical refresh action for document-scrolling protected pages.
• Per-screen override for custom scroll containers: <PullToRefresh> + usePullToRefresh() supports modals, tables with internal overflow, and pages whose scroll container isn’t the document, including passing a scrollTargetRef.
• Mobile gesture safety/guardrails: single-finger handling, direction-lock to avoid horizontal swipes, top-of-page arming, and touchmove with { passive: false } to reliably prevent native rubber-band conflicts.
• Refresh correctness for client state: PTR supports explicit callbacks for screens where router.refresh() won’t update visible client-managed data, with a recommended “Actualizar” button for accessibility.

Quick Start

Add <PullToRefresh onRefresh={refetchData}>...</PullToRefresh> inside the specific protected client screen that manages its own scroll container or client state, and call useDisableShellPTR() at the top of that screen to prevent double refresh firing.