[reeceyang]

An alternative to #278 that needs no component changes. Each aggregate starts every namespace with a name for that aggregate, e.g. ["byGame", doc.gameId] or "scores", so several aggregates can share one component.

README changes, following the structure of #278:

• All client construction examples use components.aggregate with a namespace prefix.
• "Defining multiple aggregates" moves after "Aggregate without a table" and explains the convention and its caveats:
  • Prefixes must not collide.
  • clearAll, makeAllRootsLazy, iterNamespaces and paginateNamespaces span every aggregate in the component.
  • Only one aggregate per component should omit namespace.
• The Repair section suggests clearing per namespace or changing the prefix.
• The Queued writes note says the all-or-none async/stale rule applies across the component, and shows a second component instance for queued aggregates.

The cost is that every call needs the full namespace, including aggregates that weren't namespaced before. A follow-up draft PR explores a client-side namespacePrefix that hides this.

🤖 Generated with Claude Code

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@convex-dev/aggregate@285

commit: e050806