Skip to content

Feature order previous state#98

Merged
grunch merged 1 commit into
developfrom
feature-order-previous-state
Apr 2, 2025
Merged

Feature order previous state#98
grunch merged 1 commit into
developfrom
feature-order-previous-state

Conversation

@arkanoider

@arkanoider arkanoider commented Apr 2, 2025 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Collaborator

@grunch @Catrya ,

added order previous state.

Summary by CodeRabbit

  • New Features
    • Dispute records now capture expanded context—including order history, timing, and status updates—to enhance tracking and transparency.
    • User dispute insights have been enriched with additional metrics, providing a more comprehensive view that supports improved dispute management.

@coderabbitai

coderabbitai Bot commented Apr 2, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

Caution

Review failed

The pull request is closed.

Walkthrough

The changes update the dispute-related data model by expanding the Dispute, UserDisputeInfo, and SolverDisputeInfo structs. New fields have been added to capture additional context such as order status, timestamps, tokens, ratings, and reviews. The new constructor for Dispute now requires an extra order_status parameter to initialize the order_previous_status, and the SolverDisputeInfo constructor clones this field from the dispute instance. These modifications aim to improve the accuracy and traceability of dispute data.

Changes

File Change Summary
src/dispute.rs - Dispute struct: Added fields order_id, status, order_previous_status, created_at, taken_at, buyer_token, and seller_token; updated new method to accept order_status.
- UserDisputeInfo struct: Added fields rating, reviews, and operating_days.
- SolverDisputeInfo struct: Added order_previous_status and updated the constructor to clone this field from the dispute instance.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Dispute
    participant SolverDisputeInfo

    Client->>Dispute: Call new(order_id, order_status)
    Dispute-->>Client: Return Dispute instance with new fields
    Client->>SolverDisputeInfo: Create instance using dispute data
    SolverDisputeInfo-->>Client: Return SolverDisputeInfo with order_previous_status cloned
Loading

Possibly related PRs

Suggested reviewers

  • Catrya
  • grunch

Poem

I hop through lines of code with cheer,
New fields and tokens now quite clear.
Disputes and statuses join my playful track,
With every bug and detail, I give a swift kickback.
Hopping on updates, my code sings, "All is well!"
🐰💻

📜 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 e9ed299 and e4e28a6.

📒 Files selected for processing (1)
  • src/dispute.rs (4 hunks)
✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 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.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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.

@arkanoider arkanoider closed this Apr 2, 2025
@arkanoider arkanoider reopened this Apr 2, 2025
@arkanoider arkanoider changed the base branch from main to develop April 2, 2025 12:09
@arkanoider arkanoider mentioned this pull request Apr 2, 2025
Merged
Catrya
Catrya approved these changes Apr 2, 2025
View reviewed changes

@Catrya Catrya left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tACK

@arkanoider arkanoider mentioned this pull request Apr 2, 2025
Closed
grunch
grunch approved these changes Apr 2, 2025
View reviewed changes

@grunch grunch left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@grunch grunch merged commit 36a213e into develop Apr 2, 2025
@grunch grunch deleted the feature-order-previous-state branch April 2, 2025 22:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@grunch grunch grunch approved these changes

@Catrya Catrya Catrya approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@arkanoider @grunch @Catrya