fix: align error toast color with brand#594
Conversation
Greptile SummaryThis PR aligns error toast colors with the Bitkit brand by swapping
Confidence Score: 5/5Safe to merge — a single color constant swap with no logic, data, or behavioral changes beyond the visual appearance of error toasts. The change touches exactly one return value in a pure color-mapping switch. It cannot affect dismissal logic, auto-hide behavior, or any other toast functionality. The changelog entry is accurate and the QA steps in the PR description cover both the changed path and a key regression case. No files require special attention.
|
| Filename | Overview |
|---|---|
| Bitkit/Components/ToastView.swift | One-line palette change: .error toast accent color updated from .redAccent to .brandAccent, matching .warning; no logic affected. |
| changelog.d/next/594.changed.md | New changelog fragment describing the error toast color change; content is accurate and clear. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[toast.type] --> B{switch accentColor}
B -->|.success| C[.greenAccent]
B -->|.info| D[.blueAccent]
B -->|.lightning| E[.purpleAccent]
B -->|.warning| F[.brandAccent]
B -->|.error| G[.brandAccent ← was .redAccent]
F & G --> H[same brand orange]
Reviews (2): Last reviewed commit: "fix: align error toast color with brand" | Re-trigger Greptile
Fixes #593
Description
This PR changes error toasts to use Bitkit's brand color (#FF4400) in place of the red accent (#E95164), following the design direction in #593. The design prototype renders all of its failure toasts in the brand color, and per John it is close enough to the red accent that using one color is the cleaner choice. Error and warning toasts now share the brand accent.
Linked Issues/Tasks
Fixes #593 (spun out of the color-alignment review on #592)
Screenshot / Video
QA Notes
Manual Tests
regression:Settings → Advanced → Address Viewer → long-press an address: Copied To Clipboard toast is still green.Automated Checks
N/A (one-line palette change; verified visually on the iOS simulator)