@rangojs/router 0.0.0-experimental.121 → 0.0.0-experimental.124

package/src/types/handler-context.ts

@@ -535,13 +535,24 @@ export type ActionRef =
  * downstream revalidators, or nothing (`void` / `null` / `undefined`) to defer
  * to the current suggestion without changing it.
  *
+ * Two idioms cover almost every case; they differ only in what an _unrelated_
+ * action does. Match actions by reference with `ctx.isAction()` (rename-safe)
+ * rather than `actionId?.includes("...")` (a renamed or moved action silently
+ * stops matching). Because `isAction` returns a raw boolean, combine it with
+ * `|| undefined` to defer or leave it bare to suppress.
+ *
  * @example
  * ```ts
- * // Re-render when a cart action happened or the browser signals staleness;
- * // defer otherwise (|| undefined) so the segment default still applies
- * revalidate(({ actionId, stale }) =>
- *   actionId?.includes("cart") || stale || undefined
- * )
+ * import * as CartActions from "./actions/cart";
+ *
+ * // Idiom A — "mine, else defer": re-render on my actions, otherwise return
+ * // undefined so the segment's default decision still applies (and downstream
+ * // revalidators get a say).
+ * revalidate((ctx) => ctx.isAction(CartActions) || undefined)
+ *
+ * // Idiom B — "mine only": re-render on my actions and suppress everything
+ * // else (isAction returns a raw boolean, so an unrelated action yields false).
+ * revalidate((ctx) => ctx.isAction(CartActions))
  *
  * // Always re-render when params change (default behavior made explicit)
  * revalidate(({ defaultShouldRevalidate }) => defaultShouldRevalidate)

package/src/browser/react/use-client-cache.ts

@@ -1,58 +0,0 @@
-"use client";
-
-import { useContext, useCallback } from "react";
-import { NavigationStoreContext } from "./context.js";
-
-/**
- * Return type for useClientCache hook
- */
-export interface ClientCacheControls {
-  /**
-   * Clear the client-side navigation cache.
-   * Call this after data changes that happen outside of server actions
-   * (e.g., REST API calls, WebSocket updates, etc.)
-   *
-   * This will also broadcast to other tabs to clear their caches.
-   */
-  clear: () => void;
-}
-
-/**
- * Hook to access client-side cache controls
- *
- * Use this when you need to manually invalidate the navigation cache
- * after data changes that happen outside of server actions.
- *
- * Server actions automatically clear the cache, so you only need this for:
- * - REST API mutations
- * - WebSocket-driven updates
- * - Other non-RSC data changes
- *
- * @example
- * ```tsx
- * function DataEditor() {
- *   const { clear } = useClientCache();
- *
- *   async function handleSave() {
- *     await fetch('/api/data', { method: 'POST', body: JSON.stringify(data) });
- *     // Clear cache so back/forward navigation shows fresh data
- *     clear();
- *   }
- *
- *   return <button onClick={handleSave}>Save</button>;
- * }
- * ```
- */
-export function useClientCache(): ClientCacheControls {
-  const ctx = useContext(NavigationStoreContext);
-
-  if (!ctx) {
-    throw new Error("useClientCache must be used within NavigationProvider");
-  }
-
-  const clear = useCallback(() => {
-    ctx.store.clearHistoryCache();
-  }, [ctx]);
-
-  return { clear };
-}