Repository navigation
sort on ListView renders blank repeater in Edit View Config — z.union hides items from SchemaForm 🐛 #3379
Description
Problem
In Edit View Config → Columns & Filters → Sort, clicking "Add sort" produces an empty row with no field picker or order dropdown. Users cannot configure default sort at all.
Cause
ListViewSchema.sort is defined as a union wrapping both a legacy string form and the canonical array form. The array definition ends up inside an anyOf branch, but the ObjectUI SchemaForm repeater only reads schema.items at the top level — it finds undefined and renders zero sub-fields.
Suggested fix
Drop the legacy string variant and use the canonical z.array(z.object({ field, order })) directly. The string form was already deprecated in #3373 and its removal was deferred to a separate cycle.
Related
- fix(spec): enforce ViewFilterRule operator enum with legacy-alias normalization #3373 kept the union intact intentionally
- Companion fix possible in objectui (repeater scanning
anyOfas fallback) but the spec fix is the true root cause
Metadata
Metadata
Assignees
Labels
No labels
Activity
[-]sort on ListView renders blank repeater in Edit View Config — z.union hides items from SchemaForm[/-][+]sort on ListView renders blank repeater in Edit View Config — z.union hides items from SchemaForm 🐛 [/+]os-zhuang commentedon Jul 21, 2026
Fixed by objectstack-ai/objectui#2771 (merged).
What was done — a renderer-only fix in ObjectUI's
SchemaForm. The repeater now resolves thesortunion (anyOf: [string, {field,order}[]]) to its array branch before readingitems, so the Sort field renders the field picker + order (asc/desc) dropdown instead of a blank row. Covered by a new unit test (SchemaForm.repeaterUnion.test.tsx) and verified end-to-end in a real browser (empty Sort row →Field+Ordercontrols).Scope note — the suggested spec change was intentionally not made. This issue proposed dropping the legacy bare-string variant from
ListViewSchema.sort. That was not done, becauseview.zod.tscarries an explicit instruction directly abovesort— "Removal will go through its own deprecation cycle; do not drop it here" — and the string form is kept covered by a live fixture (examples/app-showcase/.../task.view.ts, guarding objectui#2601). Dropping it would break that fixture and be a breaking change to the public spec. Per #3373 the union was kept intentionally, so the spec-side removal remains its own separate, deferred deprecation cycle and is not closed by this fix.Closing as completed since the user-facing bug (blank Sort repeater in Edit View Config) is resolved.
Generated by Claude Code