usertour

This release rebuilds how the admin app fetches and caches server data — moving apps/web off its React-Context data layer onto Apollo's normalized cache and a set of focused hooks, and unifying every list's pagination behind shared primitives. For day-to-day use the wins are freshness and stability: a teammate's edits show up without a manual refresh, the content detail page and theme builder no longer flash or go stale after a save, and the users / companies / sessions tables share one consistent, race-free pager. Under the hood this retires roughly twenty server-state Contexts and consolidates the duplicated users/companies UI.

What's Changed

🔄 Live, consistent data across the workspace

The admin app now reads through a normalized Apollo cache, so a mutation in one place updates every view showing the same record. Shared lists run cache-and-network, which means members of the same project see each other's edits without reloading.
Account email / profile changes, theme edits, and content updates now reflect immediately and in full.

✨ Content detail and theme builder stop flashing

Restoring a version or a publish-then-edit no longer blanks the content detail page mid-transition, and the theme builder reflects a theme edit the moment it saves instead of briefly showing the pre-edit state. The builder also stays mounted through background refetches rather than momentarily going blank.

📜 Unified, sturdier list pagination

Users, companies, sessions, and analytics tables now share one cursor-pagination engine. Clicking the pager faster than the network can respond no longer races into showing one page while the indicator reads the next, and bulk-deleting the rows on the last page no longer strands you on a page that no longer exists. The contents list moved to infinite scroll, and the "Load more" lists no longer collapse or double-fetch.

🚧 Explicit not-found pages

Opening a stale or invalid detail URL now shows a clear "not found" page instead of a silent blank screen.

🐛 Fixes

• Mutations that reuse a cached record no longer fail. Outgoing variables now strip the cache's __typename tag, which the server's input types had been rejecting.
• The segment-filter "Save" button hides correctly after saving, and no-op edits stop re-running queries. Condition comparison now matches the server's JSON-equivalent form instead of in-memory key differences.

🛠️ Under the hood

The apps/web data layer was reorganised end-to-end; the sections above are the visible surface, here is the shape behind them:

• Apollo InMemoryCache switched to normalized mode with per-mutation update(cache) callbacks. The app-wide default is no-cache, with an explicit SHARED_CACHE_QUERY_OPTIONS (cache-and-network) opt-in for shared lists and facade hooks. Recorded as ADR 0005 / 0006.
• The server-state-in-Context anti-pattern is retired: ~20 Context providers deleted in favour of focused hooks, AppContext is now a thin facade over identity hooks, and the remaining raw useQuery / useMutation calls are wrapped in
  @usertour/hooks.
• List pagination unified into three documented primitives — useCursorPagination (page buttons), useLoadMoreAccumulator (load-more), and a shared useCursorFetchMore request-side helper — with cache-level merge owned by typePolicy accumulators.
• Users and companies UI deduplicated into shared components/segments/entity/* components.
• apollo3-cache-persist dropped (in-memory cache only); the analytics session table's row-shared queries hoisted from per-row to per-table (~80 → 3 observers); a lighter useShouldShowMadeWith reader replaces a three-query useSubscription on theme previews.

Full Changelog: https://github.com/usertour/usertour/compare/v0.8.3...v0.8.4