Files
HealthLog/tests/integration/routes/parity/__snapshots__/analytics.01-invalid-slice.json.snap
T
Marc-André Bombeck d24c544e98 test(analytics): pin the analytics response before moving its builder
A parity walk over GET /api/analytics on an account with a full record
(record-fixture.ts, reusable by the other read routes): an unknown slice,
the summaries slice and the default body cold and warm, the modules off, a
second language with a personal blood-pressure target, an empty account and
an anonymous call. Background work a request leaves running is settled
before the next one. The blood-pressure fast path's rollup row counts are
left out of the pinned wide event: they follow the rollup tier's coverage,
not the code, while the answer they fed stays pinned in the body.
2026-10-23 13:49:24 +02:00

40 lines
699 B
Plaintext

{
"status": 422,
"cacheControl": null,
"body": {
"data": null,
"error": "Validation failed",
"details": {
"issues": [
{
"path": "slice",
"code": "invalid_value",
"message": "Invalid input: expected \"summaries\""
}
]
},
"meta": {
"errorCode": "analytics.invalid_query",
"requestId": "<requestId>"
}
},
"events": [
{
"status": 422,
"action": {
"name": "analytics.get"
},
"meta": {
"outcome": "invalid_query"
},
"warnings": null,
"error": null
}
],
"effects": [],
"stored": {
"healthScores": [],
"patterns": []
}
}