feat(payment): #4 offline payment-queue management UI#141
Merged
Conversation
The offline payment queue (paymentQueue, IndexedDB) shipped long ago but had no user-facing controls — OfflineRetryBanner is display-only and lives only on /payment-result. This adds the management layer: - PaymentQueuePanel (5-file molecular): live online/offline/syncing status, queued items with per-item retry count (Attempt N/5 → "Max retries" at the cap), a manual "Retry now" (paymentQueue.retryFailed + sync, disabled offline / when empty), and a "Clear queue" behind an inline confirmation (paymentQueue.clear). Targets paymentQueue, not the messaging queue. - Wired into /payment/dashboard behind the existing provider feature-flag gate. - E2E: un-skipped a real "queue UI renders on the dashboard" test (no creds needed — the queue is client-side); rewrote the 8 stale "UI not yet implemented" skip reasons to the actual remaining blocker (a queue-seed fixture / provider creds), since the UI now exists. Verification: type-check, lint, structure (110/110), build green; 7 component tests (empty state, item+retry-count rendering, retry→retryFailed+sync, offline-disables-retry, clear-needs-confirmation) pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #4.
What
The offline payment queue (
paymentQueue, IndexedDB via Dexie) shipped long ago but had no user-facing controls —OfflineRetryBanneris display-only and mounted only on/payment-result. This adds the management layer the issue asked for, on top of the existing backend (no new backend, no creds).PaymentQueuePanel(5-file molecular) — live online/offline/syncing status badge; queued-item list with per-item retry count (Attempt N/5→ Max retries at the cap) + last error; a manual Retry now (paymentQueue.retryFailed()+sync(), disabled when offline or empty); and Clear queue behind an inline confirmation (paymentQueue.clear()). TargetspaymentQueuespecifically — NOT the separate messaging queue./payment/dashboardbehind the existing provider feature-flag gate.E2E
"… UI not yet implemented"skip reasons in05-offline-queue.spec.tsto the actual remaining blocker: a queue-seed fixture (Dexie) or provider creds to populate the queue. The UI itself now exists — the honest accounting is "needs a seed fixture," not "not implemented."Verification
retryFailed+sync, offline-disables-retry, clear-needs-confirmation. Plus 2 a11y (empty + populated, zero axe violations).🤖 Generated with Claude Code