Skip to content
Aurora Catalyst

Add GraphQL Fetchers

Auto-generated from the source archive. Do not edit by hand — rerun catalyst-changelog-sync instead.

What changed

Section titled “What changed”
  • Seven new fetchers under @aurora/modules/graphql/fetchers/: queryPaginate, queryFindById, queryFind, queryGet, mutateCreate, mutateUpdate, mutateDeleteById. Each returns a plain Observable<T> with no signals and no dependency on a component execution context.
  • New composable useGraphqlGet for unpaginated multi-record reads — mirrors the generated getQuery / objects: shape.
  • useGraphqlFind realigned to single-record semantics (T | null) to match findQuery / object:. Plural reads now live in useGraphqlGet; no previously released composable changes its public shape.

Why it matters

Section titled “Why it matters”

Resolvers can now call GraphQL without standing up a composable. Destructure queryPagination, paginationKey, and fields from your generated *_LIST_CONFIG, invoke queryPaginate(...), and return the observable — no dead signals, no component-lifecycle contract leaking into the router. Every previously released useGraphqlX keeps the same public API, so existing components keep compiling without a single import change. The fetcher/composable split leaves a clean seam for future additions in either layer.

View original proposal