Skip to content
Sapporta

Generated query resolvers

View as Markdown

Custom table adapters can reuse the same table-dependent boundary as generated routes. The server package exports:

resolvePageQuery(query, table, { auth, searchPlan });
resolveExportQuery(query, table, { auth, searchPlan });
resolveLookupQuery(query, table);
resolveCountQuery(query, table);

These functions accept the matching parsed shared-contract query and validate table-dependent column, filter, lookup, search, and ordering semantics. The page, export, and lookup resolvers return the direct Drizzle-shaped input for the matching scopedRows() operation. Count needs one more choice:

const resolved = resolveCountQuery(query, table);
const data =
  resolved.kind === "total"
    ? await rows.count(resolved.input)
    : await rows.countBy(resolved.input);

That ResolvedCountQuery discriminator selects count() or countBy() without putting HTTP grammar into either data method. These resolvers are the right bridge when an adapter owns that grammar. Ordinary domain code should construct its Drizzle predicate directly instead of manufacturing filter[...], q, or numeric query strings.

The corresponding public types include ResolvedCountQuery and ResolveRowsQueryOptions.

Section titled “Related documentation”