Flutter’s current full-stack developer series is a useful frame for Dust too.
The repeated work is often not one widget. It is the path between the form, request model, API call, state update, and success action.
A Dust version can stay small.
Put form rules on SignupRequest with Validate(). Add Serialize() so the same request can become the HTTP body. Define the endpoint in a Dust HTTP client. Keep the submit flow in a @ViewModel.
The widget stays focused on input and UI. The request model owns validation and JSON. The API interface owns the request shape. The ViewModel owns loading, errors, and the success effect.
That is the point of using Dust across a flow. Not one large abstraction. Just repeated app glue moved into generated files that stay reviewable.
Docs used: Validation, Serde, HTTP Clients, and State Management.
Top comments (0)