[manasavkk]

Closes #64

Overview

• Added optional GraphQL filters to sort projects by length and filter by one or more project statuses using resolver JOIN logic and status-to-ID conversion.
• Add database seeding with 251 test records across 15 models
• Add production safety check to prevent accidental seeding of prod database
• Fix CI to use Docker database instead of broken Supabase credentials

Test plan

• Run npm run seed:dev to verify seeding
• Test filtering queries in Postman
• CI passes with Docker-based migrations

Testing

Tested filter combinations in Postman and verified correct sorting and results.

Screenshots / Screencasts

Postman Testing

Endpoint: POST http://localhost:3001/api/graphql

Headers:
Content-Type: application/json

1. Get all projects (no filter)

{
"query": "{ projects { project_id name description project_type } }"
}

2. Filter by status - ACTIVE only

{
"query": "{ projects(filter: { statuses: ["ACTIVE"] }) { project_id name project_type } }"
}

5. Sort by length - LONGEST first

{
"query": "{ projects(filter: { lengthSort: LONGEST_TO_SHORTEST }) { project_id name project_type } }"
}

7. Combine: ACTIVE projects sorted by longest first

{
"query": "{ projects(filter: { statuses: ["ACTIVE"], lengthSort: LONGEST_TO_SHORTEST }) { project_id name
project_type } }"
}

3. Filter by status - INACTIVE only

{
"query": "{ projects(filter: { statuses: ["INACTIVE"] }) { project_id name project_type } }"
}

4. Filter by multiple statuses (ACTIVE and INACTIVE)

{
"query": "{ projects(filter: { statuses: ["ACTIVE", "INACTIVE"] }) { project_id name project_type } }"
}

6. Sort by length - SHORTEST first

{
"query": "{ projects(filter: { lengthSort: SHORTEST_TO_LONGEST }) { project_id name project_type } }"
}

The implementation:

• Filters projects via nonprofit_chapter_project.project_status
• Calculates length as end_date - start_date (ongoing projects use current date)
• A project matches if any of its nonprofit_chapter_project entries match the status

Checklist

• Code is neat, readable, and works
• Code is commented where appropriate and well-documented
• Commit messages follow our guidelines
• Issue number is linked
• Branch is linked
• Reviewers are assigned (one of your tech leads)

Tip: You can make the issue and then check them after the fact or replace [ ] with [x] to check it!

Notes

{Any issues/suggestions relating to the ticket, repo, assignments, TL duties; please mention here!}

[manasavkk]

Fixed nonprofit status test by freezing system time in unit and integration for consistent ACTIVE/INACTIVE sorting and filtering behavior. It's ready to merge!

[soramicha]

hi manasa, please set the main branch to develop branch and add screenshots to your pr so it's easier for me to review!

[manasavkk]

PR updated and branch changed