feat(toasts): success toast on Ticket / Company / Contact create + save (MAPPS-293) #307
No reviewers
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
psa-systems/mokosh-apps!307
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/MAPPS-293-success-toasts"
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?
Successful mutations only redirected; the user had to infer success from the page change. Push a confirming success toast from the existing global toast surface (
hooks::toast::push_toast) at the three top-level create / save sites that the QA report cited - Ticket create, Company create / edit, Contact create / edit. Each surfaces a single-sentence body keyed off the form mode ("Ticket created", "Company saved", etc.). The toast root is already mounted in AppLayout so no other plumbing changes. The remaining mutation surfaces (Project, Asset, Contract, Invoice, Site, line-item edits) follow the same pattern and are tracked as a follow-up; this PR captures the highest-frequency creates.#MAPPS-293
Successful mutations only redirected; the user had to infer success from the page change. Push a confirming success toast from the existing global toast surface (`hooks::toast::push_toast`) at the three top-level create / save sites that the QA report cited - Ticket create, Company create / edit, Contact create / edit. Each surfaces a single-sentence body keyed off the form mode ("Ticket created", "Company saved", etc.). The toast root is already mounted in AppLayout so no other plumbing changes. The remaining mutation surfaces (Project, Asset, Contract, Invoice, Site, line-item edits) follow the same pattern and are tracked as a follow-up; this PR captures the highest-frequency creates. #MAPPS-293