mirror of
https://github.com/Sea-Haven-Industries/shoc-frontend-new.git
synced 2026-10-01 14:23:11 +00:00
1.8 KiB
1.8 KiB
Jira
QA residual
- Pass-UI / Blocked-BE until
additionalContactslands. Documented in pending BE contract.
Summary
- Add
additionalContacts[]({ name, phone, notes? }) across board types, table rows, wizard draft, create payload, and PATCH expansion. - Site dialog and wizard step 2 share editable primary POC fields plus + Add point of contact for POC 2+; wizard sidebar summarizes additional contacts.
- Missing backend field tolerates as
[]; normalized contacts persist viafield: "additionalContacts"JSON PATCH and POST create.
Scope
In: additionalContacts types/mappers (create, detail row, PATCH); Site dialog; wizard step 2; persist + display POC 2+.
Out: Add technician (PR7), severity (PR2/PR5), filters, uplift (PR3–PR5).
Backend contract
See docs/work-orders/pending-be-contract.md — confirm additionalContacts[] on GET board/detail, POST create, and PATCH before production. Until then FE sends typed payloads and reads missing field as [].
Test plan
- Open Site dialog on a board row → edit primary POC, add a second contact, Save → network PATCH includes
additionalContactsJSON. - New WO wizard step 2 → add additional POC → create payload includes
additionalContacts. - Reload board row with BE returning
additionalContacts→ Site dialog shows stored POC 2+. - BE omitting
additionalContacts→ no UI errors; lists render empty. npm run verifygreen.
Notes
- Primary POC remains
pocName/pocPhone/pocNotes;additionalContactsholds POC 2+ only. - Site save still PATCHes
siteCode; POC scalar fields remain local-only cache until BE exposes scalar PATCH.