Implement PATCH /distributions/:id Endpoint for Updating a Distribution

[mubarak23]

Implement functionality to update an existing distribution by ID. This involves adding an update method to the service, defining a DTO or validation schema for incoming payloads, and exposing the controller method with routing.

Folder Structure

src/
├──component/
│   ├──v1
│        ├──Distribution
│            ├── Distribution.entity.ts
│            ├── Distribution.service.ts
│            ├── Distribution.controller.ts
│            ├── Distribution.routes.ts

Scope of Work

1. Endpoint

PATCH /distributions/:id

Allows partial updates to a distribution

2. Service: updateDistribution

Create a method to:
Find the distribution by id
Apply incoming field updates
Persist changes to the database
Return updated entity

3. Controller:
   Add a controller method to:
   Accept PATCH requests at /distributions/:id
   Extract id from the URL
   Validate and parse request body
   Pass data to the service method
   Return response with 200 OK or appropriate error

4. DTO or Schema Validation:
   Create a DTO or schema for update input (optional fields)

Ensure type safety and validation (e.g., enum validation for status, numeric checks)

5. Routing:
   Register the PATCH endpoint in your routing layer (e.g., using @patch(':id') in NestJS).

Acceptance Criteria

• Proper input validation (DTO/schema) should be enforced
• Error handling and response standardization should follow project conventions
• You may stub out additional logic (e.g., metadata parsing) and implement in future issues
• Return Response Json Object with

{data: {}, success: boolan, message?: string }

[caxtonacollins]

i will love to work on this issue please assign

[Shukazuby]

Hi, I'd like to implement the PATCH /distributions/:id endpoint. I'll create an UpdateDistributionDto with proper validation, add an updateDistribution method in the service to handle partial updates, expose the controller method using @patch(':id'), and ensure response format follows { data: {}, success: boolean, message?: string }.

[yahia008]

Hi @mubarak23 ,

I'm Yahya, a backend engineer with strong experience in NestJS, DTO validation, and RESTful API design. For this task, I will implement the PATCH /distributions/:id endpoint with the following deliverables:

updateDistribution method in the service layer for partial updates

DTO for input validation (with enum/type safety)

Controller method to handle patching and return standardized responses

Proper routing using @patch(':id')

Response structure: { data: {}, success: boolean, message?: string }

✅ My estimated delivery time is within 24 hours after assignment.

[drakkomaximo]

[BE]: Implement PATCH /distributions/:id Endpoint

Hi @mubarak23 and team! I'm a Dojo Coding member ⛩️

I’d be happy to work on this functionality. I have solid experience building RESTful endpoints in Node.js/NestJS, ensuring proper input validation and clean service/controller architecture.

---

🎯 Objective

Implement a PATCH /distributions/:id endpoint that allows partial updates to an existing distribution.

---

🏗️ Steps to Implement

1) Update Service Logic

• Create updateDistribution in Distribution.service.ts.
• Find the distribution by ID.
• Apply incoming field updates, ensuring only valid fields are updated.
• Persist changes and return the updated entity.

2) Create DTO / Validation Schema

• Define a DTO (e.g., UpdateDistributionDto) with optional fields.
• Enforce proper types, including enum validation for status and numeric checks where needed.
• Ensure type safety with decorators like @IsOptional and @IsEnum.

3) Add Controller Method

• Add a PATCH route to Distribution.controller.ts.
• Use @Param to extract ID and @Body to parse/validate the request body.
• Call the service method and return the standard JSON response.

4) Register Routing

• Ensure the PATCH route is properly registered in Distribution.routes.ts or via decorators.

5) Response Format & Error Handling

• Follow the response convention: { data: {}, success: boolean, message?: string }.
• Handle 404 if the distribution ID is not found.
• Handle validation errors gracefully.

---

⏰ Estimated Time

1-2 Days

✅ Acceptance Criteria

• Partial updates work as expected.
• Input validation is robust.
• Response follows the project JSON structure.
• Proper error handling is implemented.

---

📌 Why I’m Interested

I enjoy working with NestJS and have extensive backend experience designing RESTful services with clean architecture, validation, and standardized responses.

✅ References:

BabyBeastsv2
Lyricsflip
Revolutionary Farmers
SafeTrust
Starklotto
StarShop
Timelycapsule
VolunChain

---

📬 Social Link:

Telegram: drakkomaximo

Let me know if I can start working on this right away! 🚀