fix: send measures as string array in aggregate() to match backend analytics API

[Copilot]

ObjectStackAdapter.aggregate() sends measures as [{ field, function }] but MemoryAnalyticsService.resolveMeasure() calls .split('.') on each element, expecting strings. This causes TypeError: t.split is not a function on every analytics query.

Changes

• Measure format — Convert to backend's ${field}_${function} convention (e.g. 'amount_sum'), with 'count' as special case
• Dimensions — Send [] when groupBy === '_all' instead of ['_all'] for single-bucket aggregation
• Response mapping — Rename measure keys in response (amount_sum → amount) to match aggregateClientSide() output format that consumers expect

// Before
measures: [{ field: params.field, function: params.function }],
dimensions: [params.groupBy],

// After
const measureName = params.function === 'count'
  ? 'count'
  : `${params.field}_${params.function}`;

measures: [measureName],
dimensions: params.groupBy && params.groupBy !== '_all' ? [params.groupBy] : [],

Tests

10 new tests in aggregate.test.ts covering payload format, response key mapping, all response envelope variants, and client-side fallback.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
objectui-demo	Ready	Preview, Comment	Apr 1, 2026 1:55am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
objectui	Ignored		Apr 1, 2026 1:55am

[Copilot]

Pull request overview

Fixes ObjectStackAdapter.aggregate() to match the backend analytics API’s expected request/response shape, preventing runtime failures on analytics queries and keeping aggregate results consistent for consumers (charts/dashboard widgets).

Changes:

• Send measures as a string array (['count'] or ${field}_${function} like amount_sum) instead of { field, function } objects.
• Treat groupBy === '_all' as a single-bucket aggregation by sending dimensions: [].
• Normalize analytics responses by remapping measure keys (e.g. amount_sum) back to the requested field key (e.g. amount), plus add Vitest coverage.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
packages/data-objectstack/src/index.ts	Updates analytics payload formatting and remaps returned measure keys for consumer compatibility.
packages/data-objectstack/src/aggregate.test.ts	Adds unit tests validating payload format, response normalization, envelope variants, and fallback behavior.
CHANGELOG.md	Documents the analytics aggregate compatibility fix and related behavior changes.

[Copilot]

groupBy === '_all' is now treated as “no dimensions” for the server-side analytics query, but the fallback aggregateClientSide() (used in the catch path) still groups on the literal '_all' field and will return rows containing an _all key (e.g. { _all: 'Unknown', amount: ... }). This makes the output shape differ depending on whether the analytics endpoint is available. Consider aligning the fallback behavior for '_all' (single-bucket result) so both code paths return the same row shape, and add a test for the fallback path with groupBy: '_all'.

[Copilot]

The test header comment references https://github.com/objectstack-ai/objectui/issues which points to the generic issues list, not the specific bug/issue being validated. Linking to a specific issue (or removing the link) would make it easier to trace why these tests exist.

Suggested change

	* See: https://github.com/objectstack-ai/objectui/issues (measures format bug)
	* Related to prior measures format bug in analytics payloads.