[REFACTOR]: Refactor Datafields UI to route-based edit flow (LiveView best practice) #449

New issue

Open

opened 2026-02-26 12:42:01 +01:00 by carla · 0 comments

carla commented

2026-02-26 12:42:01 +01:00

Owner

Context / Problem

On /admin/datafields we currently render overview + edit form within the same LiveView/component tree. This leads to UI inconsistencies (overview elements visible behind the edit view, modals can cause other sections to re-appear) and requires parent/child messaging to manage edit state.

Goal

Refactor the Datafields area to a route-driven flow using live_action (overview vs edit memberfield vs edit customfield).
The edit view should only show the “Datafields” header + the edit form. Overview should show both sections.
Modals (e.g. delete) must not cause the overview to re-render in the background.

## Context / Problem On /admin/datafields we currently render overview + edit form within the same LiveView/component tree. This leads to UI inconsistencies (overview elements visible behind the edit view, modals can cause other sections to re-appear) and requires parent/child messaging to manage edit state. ## Goal Refactor the Datafields area to a route-driven flow using live_action (overview vs edit memberfield vs edit customfield). The edit view should only show the “Datafields” header + the edit form. Overview should show both sections. Modals (e.g. delete) must not cause the overview to re-render in the background.