List Adoption Requests

[amina69]

📋 Description

Create an API endpoint to list adoption requests with proper filtering based on user role. Regular users see only their own requests, shelters see requests for their pets, and admins see all requests.

📝 What You'll Build

GET /adoptions Endpoint

User Perspective:

• Regular USER → See only their own adoption requests
• SHELTER → See requests for their pets
• ADMIN → See all adoption requests

Response Format:

{
  "data": [
    {
      "id": "adoption-123",
      "status": "PENDING",
      "reason": "I love dogs",
      "createdAt": "2026-02-19T10:00:00Z",
      "pet": {
        "id": "pet-456",
        "name": "Buddy",
        "species": "Dog"
      },
      "user": {
        "id": "user-789",
        "name": "John Doe",
        "email": "john@example.com"
      }
    }
  ]
}

Query Parameters (Optional)

• status - Filter by status (PENDING, APPROVED, etc.)
• petId - Filter by specific pet
• Example: GET /adoptions?status=PENDING&petId=123

🔧 Implementation Checklist

Files to Create/Modify

• src/adoption/adoption.controller.ts - Add GET endpoint
• src/adoption/adoption.service.ts - Add findAll() method
• src/adoption/dto/filter-adoptions.dto.ts - Optional filter DTO
• Update Swagger documentation
• Add unit tests

What to Build

Create Controller Endpoint:

• GET /adoptions route
• Apply JwtAuthGuard (authentication required)
• Extract user from JWT token
• Pass user info to service
• Return array of adoptions with related data

✅ Acceptance Criteria

• GET /adoptions requires authentication
• Regular users see only their own adoption requests
• Shelters see requests for pets they own
• Admins see all adoption requests
• Response includes pet details (name, species, images)
• Response includes user details (name, email, not password)
• Adoptions ordered by newest first
• Optional status filter works (?status=PENDING)
• Optional petId filter works (?petId=123)
• Returns empty array if no adoptions found (not 404)

🧪 How to Test

Setup:

1. Create 3 users (User A, User B, Shelter C)
2. Shelter C creates 2 pets
3. User A submits adoption for Pet 1
4. User B submits adoption for Pet 2

Test Scenarios:

1. User sees own requests:

   • Login as User A
   • GET /adoptions
   • Should see only User A's request for Pet 1 ✅
   • Should NOT see User B's request ❌

2. Shelter sees requests for their pets:

   • Login as Shelter C
   • GET /adoptions
   • Should see both requests (Pet 1 and Pet 2) ✅

3. Admin sees all requests:

   • Login as Admin
   • GET /adoptions
   • Should see all adoption requests ✅

4. Filter by status:

   • GET /adoptions?status=PENDING
   • Should return only PENDING adoptions ✅

5. Filter by petId:

   • GET /adoptions?petId=pet-1
   • Should return only adoptions for that pet ✅

6. No adoptions:

   • New user with no requests
   • GET /adoptions
   • Should return empty array [] ✅

7. Unauthorized access:

   • GET /adoptions without token
   • Should return 401 Unauthorized ❌

Security Reminder:

• Never return all adoptions for regular users
• Always validate user has permission to see the data
• Exclude sensitive information (passwords, secrets)

Role	What They See	Query Filter
USER	Only their requests	userId: currentUserId
SHELTER	Requests for their pets	pet.shelterId: currentUserId
ADMIN	All requests	No filter

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Sam-Rytech]

@Sam-Rytech has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi @amina69,

I would like to be assigned to Issue #21. I have experience with NestJS and implementing Role-Based Access Control to secure API endpoints.

I'm ready to start and can ensure the API follows the exact response format requested.

Thank you for considering.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Sam-Rytech to this issue.

[limitlxx]

@limitlxx has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi

I’d like to work on implementing the GET /adoptions endpoint with role-based filtering.

I have experience building secure, role-aware APIs in NestJS with proper DTO validation, Swagger documentation, and unit testing. I’ll ensure clean separation between controller and service logic while enforcing strict access control.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @limitlxx to this issue.

[anoncon]

@anoncon has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi
I’d like to work on this issue if it’s available. I’m a full-stack Web2 & Web3 developer with solid open-source experience and can start working on it right away.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @anoncon to this issue.

[adewuyito]

@adewuyito has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Good sir, might i be vested the authority to vanquish they issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @adewuyito to this issue.

[drips-wave]

Congratulations, @anoncon! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @anoncon: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are issued when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊