Server admin follow-up: per-field errors for the community Overview form (core) #749

Open
opened 2026-11-16 04:41:34 +00:00 by charles · 0 comments
Owner

From the review of PR #739 (Task 23, #691), seen on 7e6fdf9a.

The plan's Task 23 asks for field errors under their fields, but Task 11's form model (fluxer-core admin::form::Form / admin::guild Overview) has no per-field errors: a refused save (e.g. an invalid name) only sets the form-wide error shown in the unsaved-changes bar, so the UI passes None as the name field's error.

To do (fluxer-core first, then fluxer-ui): map the server's field errors (errors of the 400 body, e.g. name) onto the Overview fields in core, expose them in OverviewModel, and draw them under the fields in screens/entity_settings/guild/overview.rs.

Refs #691

From the review of PR #739 (Task 23, #691), seen on 7e6fdf9a. The plan's Task 23 asks for field errors under their fields, but Task 11's form model (`fluxer-core` `admin::form::Form` / `admin::guild` Overview) has no per-field errors: a refused save (e.g. an invalid name) only sets the form-wide error shown in the unsaved-changes bar, so the UI passes `None` as the name field's error. To do (fluxer-core first, then fluxer-ui): map the server's field errors (`errors` of the 400 body, e.g. `name`) onto the Overview fields in core, expose them in `OverviewModel`, and draw them under the fields in `screens/entity_settings/guild/overview.rs`. Refs #691
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/fluxer-native#749
No description provided.