feat(SchemaForm): field-type-aware operator + value widgets for view filter

[akarma-synetal]

Summary

• ResourceEditPage: reads draft.data.object so view filter rows get object field catalog
• SchemaForm: detectOperatorWidget + detectValueWidget name-convention detectors
• widgets.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

• Edit View Config filter: operator shows human-readable dropdown narrowed by field type
• Value input adapts to field type (boolean toggle, number input, date picker)
• Unary operators (is_empty, is_null) show disabled placeholder
• Between operator shows from/to range inputs

Made with Cursor

[vercel]

@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.

[os-zhuang]

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 main), tracked by #2764.

The rework reuses the existing runtime FilterBuilder (via the filter-builder widget) rather than adding parallel per-row operator/value widgets, which avoids a few issues in the original:

• No duplication of FilterBuilder. The runtime builder already provides per-field-type operator lists, type-aware value inputs (boolean/number/date/select, multi-value for in), and i18n. Routing is done contract-first by pinning widget: 'filter-builder' on the view filter field in the spec form (framework#3373), matching dataset/page.
• Operator vocabulary is unified with the canonical @objectstack/spec ViewFilterRule enum. FilterBuilderWidget writes canonical operators; the runtime maps (ListView.mapOperator, UserFilters.specOperatorToAst) accept them.
• Avoids the specific bugs in the parallel widgets: between unreachable for date fields (branch-order), booleans stored as "true"/"false" strings, in/not_in stored as comma-joined strings, literal — rendered in JSX, hardcoded English labels, and over-broad /Value$/ / /Operator$/ detection.
• Kept the useful bit from here: resolving the source object from draft.data.object so filter rows get the field catalog.

Depends on framework#3373 (the operator enum + form widget pin), which is also merged. Since the change is on main via #2766, this PR can be closed as superseded. Thanks again for kicking this off.

---

Generated by Claude Code