You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(data-fabric): route expansionLevel to URL query string on queryRecordsById (#531)
* fix(data-fabric): route expansionLevel to URL query string on queryRecordsById
DF record POST endpoints honour `expansionLevel` only as a URL query
param, not from the request body. The rest of the query options (filters,
sort, aggregates, etc.) are still sent in the POST body.
Adds a generic `urlParams` hook to PaginationHelpers.getAll that keeps
declared keys in the URL query string regardless of HTTP method — body on
POST, merged into params on GET — for both the paginated and non-paginated
flows. `queryRecordsById` wires `expansionLevel` through it so non-zero
levels actually expand reference fields again.
Also stops base.ts from folding caller `options.params` into the POST body
and nulling out the URL params, so URL query params survive on POST.
Adds two integration tests covering all expansion levels (0-3): one for
the system reference field `CreatedBy`, and one that builds an isolated
source→target schema with a custom RELATIONSHIP field to verify the
user-defined column inflates per level.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* test(data-fabric): skip RELATIONSHIP expansion test under PAT auth
entities.create() needs the entity.schema.write scope, which PAT tokens
cannot hold (returns insufficient_scope). The CreatedBy expansionLevel
test already validates the fix under PAT; keep this body for OAuth runs.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* refactor(pagination): rename urlParams to queryParams
queryParams is the recognized HTTP nomenclature and the existing
convention in this codebase for query-string params passed via params:
(see process-instances.ts, buckets.ts). urlParams elsewhere refers to
URLSearchParams over window.location — a different concept.
Also re-skip the RELATIONSHIP expansion integration test (needs
entity.schema.write, unavailable to PAT) and refine the queryRecordsById
comment.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* test(data-fabric): use describe.skip for RELATIONSHIP expansion test
Match the file's convention for schema-write tests (describe.skip), which
need the entity.schema.write scope PAT tokens can't hold. it.skip on a
lone test was inconsistent with the surrounding describe.skip blocks.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0 commit comments