Seller can rate buyer after release funds

[grunch]

Buyer still needs to be wait to receive sats
then mostro will send the rate message to buyer

Fix #417

Summary by CodeRabbit

• New Features

  • Enhanced transaction rating system by sending direct messages to both buyer and seller after order completion

• Changes

  • Updated payment success workflow to streamline rating process
  • Simplified payment handling by removing unnecessary key extraction

• Refactor

  • Removed standalone counterpart rating function
  • Adjusted messaging logic for transaction ratings

[coderabbitai]

Walkthrough

The pull request modifies the release and rating mechanism in the Mostro application. The primary changes involve adjusting how counterpart ratings are handled after a transaction. The rate_counterpart function in src/util.rs has been removed, and the rating logic has been integrated directly into the payment_success and release_action functions in src/app/release.rs. The changes aim to prompt users to rate their counterpart immediately after the seller releases the funds, rather than waiting for the buyer to receive the payment.

Changes

File	Change Summary
src/app/release.rs	- Simplified do_payment function by removing seller's public key extraction - Updated payment_success function signature (removed seller_pubkey) - Added direct messaging for counterpart rating after order update
src/util.rs	- Removed rate_counterpart function entirely

Assessment against linked issues

Objective	Addressed	Explanation
Rate counterparty immediately after seller releases sats [#417]	✅

Possibly related PRs

• Get the right next trade fields on release #422: Get the right next trade fields on release
• Code optimization on release #424: Code optimization on release

Poem

🐰 Hop, hop, release the sats with glee,
A rating prompt, now swift and free!
No more waiting, no delay,
Counterparts rate without dismay,
Mostro's magic, transaction's spree! 🌟

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 09648f9 and c03ff2c.

📒 Files selected for processing (2)

• src/app/release.rs (5 hunks)
• src/util.rs (0 hunks)

💤 Files with no reviewable changes (1)

• src/util.rs

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: tests

🔇 Additional comments (4)

src/app/release.rs (4)

182-191: Well-placed rating prompt for sellers!

The addition of the rating message right after funds are released is a logical placement that aligns well with the user flow.

---

276-278: Clean refactoring of buyer pubkey extraction!

The code maintains proper error handling while moving the buyer pubkey extraction earlier in the function flow.

---

294-296: Clean function signature!

Removed unused seller_pubkey parameter, making the function signature more focused.

---

343-353: Verify the order update and rating message atomicity.

The rating message is correctly sent after the order update. However, let's verify that there are no edge cases where the rating message could be sent without a successful order update.

Run this script to check for similar patterns in the codebase:

✅ Verification successful

Order update and rating message atomicity is properly implemented

The code correctly ensures that the rating message is sent only after a successful order update. The implementation uses proper error handling with if let Ok() and follows consistent patterns found throughout the codebase. No edge cases were found where the atomicity could be violated.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for consistent order update and message sending patterns

# Look for patterns where order updates and message sending are paired
ast-grep --pattern 'if let Ok($result) = $order.update($pool).await {
  $$$
  send_new_order_msg($$$)
  $$$
}'

# Look for any potential message sends without order updates
rg -B 5 'send_new_order_msg.*Action::Rate'

Length of output: 157

---

Script:

#!/bin/bash
# Search for order updates with more flexible pattern
ast-grep --pattern '$order.update($$$).await'

# Search for rating message sends with more context
rg -B 10 -A 5 'send_new_order_msg.*Action::Rate'

# Search for order update patterns
rg -B 10 -A 5 '\.update\(&pool\)\.await'

Length of output: 5188

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.