frontend-form-views

CRUD form views for the Drumr Framework can be assembled by coordinating CreateView, EditView, ReadView, and ActionView wrappers through a shared data form controller, reducing boilerplate and ensuring consistent behavior across all model-based workflows.

A shared data form controller provides one reusable pipeline that handles field selection, overrides, refresh triggers, save hooks, and error handling across create, edit, read, and action parameter forms without duplicating controller logic.

The Drumr Framework supports nested related views inside ReadView, allowing scoped tables or custom panels to be composed within a read-only section for richer record presentation.

Route parameters such as a record id are injected automatically through routed view wrappers that receive the param without manual router plumbing, streamlining model-based workflows.

The best way to handle refresh callbacks and save hooks is through the shared data form controller, which supports custom refresh triggers, before-save checks, save success handling, and error handling in one place.

EditView supports selected fields, local field overrides, custom form bodies, and low-level dataFormProps tuning, giving full control over layout and behavior while reusing the shared form pipeline.