Review & Rating System for Sellers

[Villarley]

🧩 Issue 1: Trustless Work Provider Setup

🎯 Objective

Integrate the Trustless Work React library provider so hooks can be used app-wide.

⚙️ Config

.env:

NEXT_PUBLIC_TW_API_KEY

NEXT_PUBLIC_TW_BASE_URL (default: https://dev.api.trustlesswork.com)

🧱 Implementation

Create src/providers/trustless-work-provider.tsx

Wrap App.tsx (or app/layout.tsx) with

✅ Rules

Provider must load before any hooks are called

Fail fast if no API key

🧪 Tests

✅ Provider mounts without error

❌ Missing API key throws

✅ Definition of Done

[davedumto]

Hi, my name is David, and I am a frontend developer skilled in React, Next.js, TypeScript, and Tailwind CSS. For this task, I will:

• Implement the review and rating system for sellers, ensuring buyers can rate (1–5) and review sellers only after confirming a purchase.
• Create the reviews table with proper schema, validations, and foreign key relations as described.
• Build the POST /reviews endpoint to allow buyers to submit a single review per confirmed offer.
• Build the GET /users/:id/reviews endpoint to retrieve reviews with relational data for buyer and offer.
• Implement validation rules to ensure ratings are between 1–5, prevent duplicate reviews, and enforce buyer-ownership rules.
• Update the seller profile to display aggregated ratings and reviews.
• Include unit and integration tests for submission, validation, and aggregation logic.

ETA: 36 hours for draft PR

~ OnlyDust Stellar Fellow

Recommended by OnlyDust for high-quality and dependable contributions.

[0xDeon]

Gm gm team,

I'd love to work on this feature. I will start by ensuring that buyers can leave a single review per confirmed offer, with proper validation in place to enforce rating bounds and prevent duplicates. I’ll handle the relational fetches to include buyer and offer details in the response, and I’ll make sure the average rating is accurately exposed in the seller’s public profile to reflect their reputation.

I’ll also write comprehensive tests to cover the full flow, from review creation to rating aggregation, and make sure everything aligns with the existing project structure.

Recommended by OnlyDust for outstanding experience and quality contributions.

[LaGodxy]

Hi @Villarley , I’d like to work on this.
Plan: implement the reviews table, add POST /reviews and GET /users/:id/reviews with validation (rating 1–5, one review per confirmed offer), and expose aggregated ratings on seller profiles.
I’ll open a draft PR within 36 hours.

[FabianSanchezD]

Hi @Villarley, I'm Fabian Sanchez and I'd like to work on this issue. I have experience with backend issues similar to this one, and I have previously contributed to Starshop, thanks!

[Jafet2do]

Hi I’m a student pursuing a engineering-admin degree in software development, i would love to contribute, to improve my skills.

[Gabo0510]

Hi I’m Gabriel Meza a student pursuing a engineering-admin degree in software development, I would love to contribute, to improve my skills

[laryhills]

Hi team, I’d love to take this one!

✅ Plan: I’ll add a reviews table (per spec), create POST /reviews and GET /users/:id/reviews with validations (@Min(1), @Max(5)), enforce rules (buyer-only, one review per offer, offer must be confirmed), and compute seller average rating for profile responses. I’ll include relational data (buyer, offer) in GET, prevent duplicates at DB + service layer, and write tests for allowed/blocked cases.

📌 Why Me: I’ve built ratings/reviews systems with strict business rules and aggregation before (NestJS + TypeORM), ensuring data integrity, clean APIs, and reliable test coverage.

Recommended by OnlyDust for high-quality and dependable contributions.

[BrandonRodzz]

Hi I’m a student pursuing a engineering-admin degree in software development, i would love to contribute, to improve my skills

[nikkybel]

Hi, my name is Nikkybel, and I am a ful-stack developer skilled in React, Next.js, TypeScript, and Tailwind CSS. For this task, I will:

Implement the review and rating system for sellers, ensuring buyers can rate (1–5) and review sellers only after confirming a purchase.
Create the reviews table with proper schema, validations, and foreign key relations as described.
Build the POST /reviews endpoint to allow buyers to submit a single review per confirmed offer.
Build the GET /users/:id/reviews endpoint to retrieve reviews with relational data for buyer and offer.
Implement validation rules to ensure ratings are between 1–5, prevent duplicate reviews, and enforce buyer-ownership rules.
Update the seller profile to display aggregated ratings and reviews.
Include unit and integration tests for submission, validation, and aggregation logic.

[gelluisaac]

hi am a software developer i would want to work on this issue

Recommended by OnlyDust for high-quality and dependable contributions.