feat(forms): migrate remaining create/edit forms to FormGuard (PMS-518) #356
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/PMS-518-remaining-forms"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Bulk PMS-518 increment: migrates the remaining create/edit form surfaces onto the shared
FormGuard, so every form reports its failures together (per-field inline slots) and focuses the first invalid field.Forms migrated
note_invalid). Inline onchange editors left as-is (they PUT on change, not form submits).validate_*validators.note_invalid). The Log Time create form was already migrated.[Rule::Required, Rule::Email]into an inline slot.Strategy
guard.field(...)per field.Decimal/String/date values the body uses) and only added focus-first viaFormGuard.A couple of messages were standardized to the canonical
Rulewording so blur-time and submit-time agree (e.g. "Status is required."). Values sent to the server are unchanged (only the required-check is trimmed).How it was built
Five parallel per-file migrations (one subagent per file), then verified centrally.
Verification
just checkparity via the rust-builder image:clippy --all-targets -- -D warnings,fmt --check,cargo check --target wasm32-unknown-unknown- all green.