Uh oh!
There was an error while loading. Please reload this page.
fix: normalize reader output - #217
Conversation
Greptile SummaryThe PR moves Appwrite column normalization to the SDK list-model boundary while preserving the reader’s plain-array output contract.
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains. Important Files Changed
Reviews (2): Last reviewed commit: "Merge branch 'main' into fix/reader-norm..." | Re-trigger Greptile |
abnegate
commented
Aug 12, 2026
Latest-compatible dependency audit at exact head
This was a disposable compatibility resolution only; no VCS pin or lock-file change is being added to this PR. The full local suite was not counted as a pass because its NHost and Supabase E2E services were not running (8 connection errors); the PR's own current-head CI remains the authoritative full gate. |
Uh oh!
There was an error while loading. Please reload this page.
Summary
Changes
ColumnListmodel instead of serializing each raw entry independently.API::listColumns()with realDatabaseandTableresources and the locked Appwrite SDK 26.1.0 model.Scope in the DAT-2310 release train
This is a consumer-boundary compatibility leaf, not the production empty-object fix by itself. It ensures the migration reader keeps returning
list<array>when the SDK list model materializes polymorphic column entries as already-normalized arrays. DAT-2310 still requires the coordinated HTTP, database, Mongo, server-ce, and cache fixes before an empty JSON object can be called preserved end to end.Test plan
Refs DAT-2310