fix(ui): prevent stacking banners during wallet identity search#734
fix(ui): prevent stacking banners during wallet identity search#734thepastaclaw wants to merge 1 commit into
Conversation
…pay#713) Add BackendTaskSuccessResult::Progress variant for progress messages that should update the existing banner instead of creating new global banners. Change load_user_identities_up_to_index to send Progress instead of Message for "Searching index X of Y..." updates. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
@coderabbitai review |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughA new Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
✅ Actions performedReview triggered.
|
|
Closing as duplicate of #735, which has the more targeted fix. Sorry for the duplicate — improving my dedup guards to prevent this. |
Summary
Fixes #713 — "Load identity: load from wallet displays messy messages."
When searching a wallet for identities up to a given index, each progress update ("Searching index X of Y...") was sent as a
BackendTaskSuccessResult::Message, which triggeredMessageBanner::set_global()inapp.rs— creating a new green success banner for every iteration. These banners stacked up, cluttering the UI.Changes
BackendTaskSuccessResult::Progress(String)— a new variant for progress messages that should NOT create global bannersapp.rs— handleProgressby forwarding to the screen'sdisplay_task_resultonly (noMessageBanner::set_global)load_identity_from_wallet.rs— change the loop's progress sends fromMessagetoProgressadd_existing_identity_screen.rs— handleProgressby updatingbackend_message(rendered inline as a label, not a stacking banner)Validation
cargo checkpassescargo fmtpassesProgressvariant skipsMessageBanner::set_globalinapp.rs(line 1115)backend_messageis rendered inline at line 1143 as"{progress_msg} ({elapsed})"— single updating label, no stackingSummary by CodeRabbit