Skip to content

fix: make inbox order status sticky and visible#17

Merged
eurobuddha merged 1 commit intomasterfrom
fix/inbox-status-sticky
Mar 23, 2026
Merged

fix: make inbox order status sticky and visible#17
eurobuddha merged 1 commit intomasterfrom
fix/inbox-status-sticky

Conversation

@eurobuddha
Copy link
Copy Markdown
Owner

Summary

  • showMessageDetail() now pre-populates #status-selector with the message's actual current status — previously it always defaulted to PENDING, so clicking "Update Status" without touching the dropdown silently overwrote real statuses back to PENDING
  • Status badge added to each message list item (colour-coded: yellow=pending, blue=paid, green=confirmed, purple=shipped, teal=delivered) so changes are visible without reopening the order

Root cause

The SQL write in updateMessageStatus() was working correctly all along. The bug was that the selector was never seeded with the saved value on modal open, making it appear as though status changes weren't persisting.

Test plan

  • Set an order to Confirmed, close modal — badge should show ✅ CONFIRMED in the list
  • Reopen same order — status selector should show Confirmed, not Pending
  • Change to Shipped and update — badge updates, reopening still shows Shipped

🤖 Generated with Claude Code

- showMessageDetail() now pre-populates #status-selector with the
  message's current status so clicking Update Status doesn't silently
  reset it back to PENDING
- Add status badge to each message list item so status changes are
  immediately visible without opening the order
- Add CSS classes for each status (pending/paid/confirmed/shipped/delivered)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@eurobuddha eurobuddha merged commit 6ea5566 into master Mar 23, 2026
5 checks passed
@eurobuddha eurobuddha deleted the fix/inbox-status-sticky branch March 23, 2026 14:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant