Summary
Changing a field's type in the FormBuilder (e.g., single_choice → text) silently drops type-dependent attributes (the options array). If the user switches back, those options are lost. Currently no warning surfaces.
Requirements
Context
Plan 4 review follow-up. v2 polish — the current behavior is intentionally destructive (server is the source of truth, attributes irrelevant to the type don't persist), but a one-way silent loss is poor UX.
Files
apps/admin/src/components/FormBuilder.tsx (type change handler)
Summary
Changing a field's type in the FormBuilder (e.g.,
single_choice→text) silently drops type-dependent attributes (theoptionsarray). If the user switches back, those options are lost. Currently no warning surfaces.Requirements
Context
Plan 4 review follow-up. v2 polish — the current behavior is intentionally destructive (server is the source of truth, attributes irrelevant to the type don't persist), but a one-way silent loss is poor UX.
Files
apps/admin/src/components/FormBuilder.tsx(type change handler)