Summary
When creating a new View via the metadata admin UI, the Object field renders as a plain <input type="text"> instead of a <Select> dropdown that lets the user pick from existing objects.
Root cause
In packages/app-shell/src/views/metadata-admin/anchors.ts, lines 217-221, the View createSchema defines object as:
object: {
type: 'string',
title: 'Object',
description: 'The object this view displays.',
}
It's missing widget: 'ref:object'. SchemaForm interprets plain type: 'string' as a text input. The Page type (same file, lines 147-152) correctly includes widget: 'ref:object' on its object field — View does not.
Steps to reproduce
- Navigate to Metadata → View → Create new
- Observe the "Object" field — it's a plain text input
- Compare with Page → Create new — the "Object" field is a proper dropdown
Expected behavior
The Object field renders as a <Select> dropdown populated with existing objects.
Fix
Add widget: 'ref:object' to the object property in View's createSchema (line 220).
Impact
Every user creating a View must manually type the object name instead of picking from a dropdown. Typo-prone, bad UX.
Summary
When creating a new View via the metadata admin UI, the Object field renders as a plain
<input type="text">instead of a<Select>dropdown that lets the user pick from existing objects.Root cause
In
packages/app-shell/src/views/metadata-admin/anchors.ts, lines 217-221, the ViewcreateSchemadefinesobjectas:It's missing
widget: 'ref:object'. SchemaForm interprets plaintype: 'string'as a text input. The Page type (same file, lines 147-152) correctly includeswidget: 'ref:object'on itsobjectfield — View does not.Steps to reproduce
Expected behavior
The Object field renders as a
<Select>dropdown populated with existing objects.Fix
Add
widget: 'ref:object'to theobjectproperty in View'screateSchema(line 220).Impact
Every user creating a View must manually type the object name instead of picking from a dropdown. Typo-prone, bad UX.