Conversation
…ch Stellar address format expectations.
…o forced lowercasing).
…project IDs efficiently.
…g Supabase metadata.
…g Supabase metadata.
…completion before client approval.
…d correct error message assertions.
…t to match new workflow.
…roval in full workflow.
…ilestone badge variant mapping for Completed status.
…e badge variant for Completed status.
…pdate milestone badge variant mapping.
…ading state, and success notification.
… milestone completion.
… fetch and application submission.
…th, status updates, and error cases.
…ver with dispute resolution logic.
…onent in listing creation page.
…onent in client dashboard.
…onent in direct project creation page.
…onent in freelancer dashboard.
…ne card with locked funds messaging.
…o settle disputes.
…tions including auth and state transitions.
…tion UI across protected pages.
…on index, and metadata validation.
…resolve_dispute functions, and test count.
…ponent, and updated contract ID.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
johneliud
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Implements the full freelancer completion gate (mark_complete → approve), admin dispute resolution, a shared WalletGuard component, tighter Supabase RLS policies, and redeployment of the updated contract to testnet.
Type of Change
Changes Made
initialize(resolver)one-time setup,mark_complete(Funded → Completed, freelancer-only), andresolve_dispute(Disputed → Released, resolver-only);approve_milestonenow requiresCompletedstatus instead ofFundedResolverkey toDataKeyenum; 15 new tests acrossmark_complete.rsandresolve_dispute.rs(50 total, all passing)markCompleteandresolveDisputefunctions tolib/contract.tsWalletGuardcomponent — replaces ~100 lines of duplicated inline wallet prompts across 4 pagescompleted(amber) badge variant toBadge.tsxconsole.errorto all try/catch blocks; added success toast for application rejection20260607000000_tighten_rls_policies.sql— status check constraints, tighterUSINGclauses on update policies, unique index on(listing_id, freelancer_address)CAYB22PI2YRQPW4VGCX34XSCKMHNPERQYXIJ6Z2OZ3YKISW4XG2DSLIU;initializecalled with deployer as resolver.envfiles updated with new contract IDRelated Issue
Closes #49
Closes #51
Closes #52
Testing
cargo testpasses — 50 tests, 0 failednpx tsc --noEmitpasses — 0 errorsChecklist
.env.exampleupdated if new env vars were added