Skip to content

fix: reject DisputeOutcome::Pending as valid resolution outcome (#719) - #745

Open
Kenlachy wants to merge 1 commit into
ThinkLikeAFounder:mainfrom
Kenlachy:fix/719-pending-resolution-outcome
Open

fix: reject DisputeOutcome::Pending as valid resolution outcome (#719)#745
Kenlachy wants to merge 1 commit into
ThinkLikeAFounder:mainfrom
Kenlachy:fix/719-pending-resolution-outcome

Conversation

@Kenlachy

Copy link
Copy Markdown

Prevents logically inconsistent state where dispute.status = Resolved but dispute.outcome = Pending. Added validation check in resolve_dispute to panic if Pending is used as a resolution outcome.

…kLikeAFounder#719)

Prevents logically inconsistent state where dispute.status = Resolved
but dispute.outcome = Pending. Added validation check in resolve_dispute
to panic if Pending is used as a resolution outcome.

- Add validation to reject DisputeOutcome::Pending
- Remove Pending from match arm (now rejected earlier)
- Add test to verify the fix
@drips-wave

drips-wave Bot commented Jul 28, 2026

Copy link
Copy Markdown

@Kenlachy Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

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.

[bug] dispute-resolution: DisputeOutcome::Pending can be used as a final resolution outcome — creates logically inconsistent state

1 participant