Admin reports: filter by reason and sort order

Abierto
#142 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
58/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
mongodb, nodejs, react, typescript
Área
full-stack

Línea de trabajo

Start with useAdminReports(status) in apps/web/src/pages/AdminPage.tsx and the admin reports handler in apps/api/src/controllers/adminController.ts, then read the Report model in apps/api/src/models/Report.ts to see which fields can be filtered. Add reason and order query parameters next to status, validated with Zod, keeping cursor paging. Done means invalid values return 400, filters combine, admin-only access still passes existing tests, and each filter has a test.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

api enhancement help wanted web

Difficulty: Intermediate · Estimated size: 1 day

Context

The Admin page lists reports on posts and already filters by status (see useAdminReports(status) in AdminPage.tsx). With many reports it is still hard to find the ones that need attention.

Problem or goal

Let admins also filter by reason and choose the sort order (newest or oldest first).

Suggested approach

  • API: accept reason and order query parameters (keep status) on the admin reports endpoint, validated with Zod, and keep cursor paging.
  • Web: a small filter bar on the Reports tab that remembers the choice for the session, with a clear empty state.

Where to look

  • apps/api/src/controllers/adminController.ts
  • apps/api/src/models/Report.ts
  • apps/web/src/pages/AdminPage.tsx

Acceptance criteria

  • Invalid filter values return 400.
  • Filters combine correctly.
  • Only admins can call it (existing tests keep passing).
  • A test for each filter.

How to work on it

  1. Comment here to claim it, so two people do not do the same work.
  2. Fork the repo and branch from main (feat/short-name or fix/short-name). Setup steps are in docs/DEVELOPMENT.md.
  3. Keep the change focused and add tests for backend logic.
  4. Run npm run typecheck, npm test and npm run lint and npm run format before opening the pull request.
  5. Use a Conventional Commits title (for example feat(web): add bookmarks). More in CONTRIBUTING.md.

Stuck? Ask in this issue. Questions are welcome.


Generated by Claude Code

Lenguaje dominante
TypeScript
Estrellas
6
Forks
6
Merge medio
1 h 59 min
PR fusionados (30 d)
59

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Haseeb-MernStack/commune

Todos los issues de Haseeb-MernStack/commune

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.