Skip to content

fix(ui): restore user-solver chat exports after merge - #128

Merged
arkanoider merged 1 commit into
mainfrom
fix/post-merge-clippy-user-solver-chat
Aug 16, 2026
Merged

fix(ui): restore user-solver chat exports after merge#128
arkanoider merged 1 commit into
mainfrom
fix/post-merge-clippy-user-solver-chat

Conversation

@arkanoider

Copy link
Copy Markdown
Collaborator

Summary

  • Re-export UserChatChannel from crate::ui and restore missing imports (save_user_dispute_chat_message, FOOTER_MYTRADES_TAB_CHAT) broken by the feat(chat): add user-to-solver dispute chat #119 merge.
  • Restore My Trades Tab / BackTab peer↔solver chat toggling that was dropped during the merge conflict resolution.

Test plan

  • cargo fmt --all
  • cargo clippy --all-targets --all-features -- -D warnings
  • cargo test --all-features
  • cargo build --all-features
  • Manually: on My Trades with an assigned solver, Tab/BackTab switches Peer ↔ Solver chat; without a solver, Tab stays on Peer.

Made with Cursor

Re-export UserChatChannel and restore My Trades Tab/BackTab peer↔solver
toggling dropped by the #119 merge, plus missing helper/constant imports
so clippy and tests pass again.

Co-authored-by: Cursor <cursoragent@cursor.com>
@arkanoider arkanoider added bug Something isn't working rust Pull requests that update rust code labels Aug 16, 2026
@coderabbitai

coderabbitai Bot commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@arkanoider, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 46b2adcf-c8db-4214-aef0-d0450c6055c0

📥 Commits

Reviewing files that changed from the base of the PR and between f37d836 and b94d4a6.

📒 Files selected for processing (4)
  • src/ui/key_handler/enter_handlers.rs
  • src/ui/key_handler/navigation.rs
  • src/ui/mod.rs
  • src/ui/tabs/order_in_progress_tab.rs

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@arkanoider
arkanoider merged commit dd55147 into main Aug 16, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant