Overview - Query

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
11394
0687fdab feat(solid-query): sweep X-Revalidate keys in the single-flight consumer A mutation can declare its invalidation scope with X-Revalidate keys (Solid's reload/redirect `revalidate` option). The flight payload covers the part of that scope the server's collector recomputed — typically the target page's loader graph — but a declared key can match more than any loader knows about: parameterized instances only the client holds (['users', 2] behind a paginated list), queries no loader owns (a layout's notification count). Those previously stayed stale until their own staleTime brought them back. The provider's flight consumer now finishes the job client-side: after hydrating the payload, each declared key is invalidated by queryKey prefix — active queries refetch in the background, inactive ones are marked stale for their next mount — with payload-covered hashes exempt (they hydrated with fresh data a moment ago; refetching them would spend the round trip single flight just saved). This mirrors how Solid Router consumes the same header for its own cache, so one `revalidate` declaration on a mutation scopes both caches consistently. No wire or protocol changes: the keys already ride the response headers the consumer receives as envelope context. Collectors should contribute their slice even when it holds no queries if outcome.revalidateKeys is present — the sweep is delivered with the slice (documented on FLIGHT_DATA_SOURCE). Co-authored-by: Cursor <cursoragent@cursor.com>
by Ryan Carniato