feat(SchemaForm): field-type-aware operator + value widgets for view filter#2760
feat(SchemaForm): field-type-aware operator + value widgets for view filter#2760akarma-synetal wants to merge 1 commit into
Conversation
…filter - ResourceEditPage: read draft.data.object for view resources so the object field catalog is populated (was always empty for standalone views, breaking type-aware widget rendering). - SchemaForm: add detectOperatorWidget + detectValueWidget name- convention detectors that intercept `operator` / `value` fields inside a filter repeater row and render custom widgets. - widgets.tsx: OperatorWidget (field-type-aware operator dropdown with human-readable labels matching FilterBuilder) and ValueWidget (type- aware input: boolean→toggle, number→number input, date→date picker, between→range, in→comma-separated, unary→disabled placeholder). Co-authored-by: Cursor <cursoragent@cursor.com>
|
@akarma-synetal is attempting to deploy a commit to the Object Stack Team on Vercel. A member of the Team first needs to authorize it. |
|
Thanks for this — the UX gap it targets (field-type-aware operators + value inputs for view filter rows, instead of raw text) was real, and it shipped in a reworked form via #2766 (now merged to The rework reuses the existing runtime
Depends on framework#3373 (the operator enum + form widget pin), which is also merged. Since the change is on Generated by Claude Code |
Summary
ResourceEditPage: readsdraft.data.objectso view filter rows get object field catalogSchemaForm:detectOperatorWidget+detectValueWidgetname-convention detectorswidgets.tsx:OperatorWidget(labels match FilterBuilder, per-type operator filtering) +ValueWidget(boolean→toggle, number→number, date→date picker, between→range, in→comma, unary→placeholder)Test plan
Made with Cursor