AOSSIE-Org / AOSSIE-Org/OrgExplorer

[BUG]: No "no results" message shown when filters match zero repositories

Abierto Apto para principiantes
#193 4 comentarios 0 reacciones 0 asignados Ver en GitHub
bug
Lenguaje dominante
JavaScript
Estrellas
34
Forks
92
Merge medio
8 d 7 h
PR fusionados (30 d)
12

Descripción

### Bug Description

When search or filter selections on the Repository Explorer page match zero repositories, the table renders with only the header row and no rows underneath there is no message telling the user that no repositories matched their filters. The empty state component only triggers when the organization has zero repositories overall, not when
a filter simply returns zero matches from a non-empty repository list.

### Steps to Reproduce

1. Go to the Repositories page for any organization with repositories
2. Type a search term that won't match any repository name or description (e.g. "xyz")
3. See the repository count update to "0 / 442 repos" (or similar)
4. Notice the table shows only the header row, with a blank area underneath and no explanation

### Logs and Screenshots

Screenshot attached: searching "xyz" shows "0 / 442 repos" in the header, but the table body is completely empty with no "no results" message.

## screenshot

Image

### Environment Details

- OS: Windows 11 / macOS / Linux
- Browser: Chrome 120 / Firefox / Safari
- Relevant file: src/pages/RepositoriesPage.jsx

### Impact

Critical - Application is unusable

### Code of Conduct

- [x] I have joined the [Discord server](https://discord.gg/hjUhu33uAn) and will post updates there
- [x] I have searched existing issues to avoid duplicates

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Open src/pages/RepositoriesPage.jsx and reproduce the issue by searching for “xyz” on an organization with repositories. Trace the existing empty-state condition for zero repositories versus zero filtered matches. Done means the Repository Explorer shows a clear no-results message when filters match zero repositories while retaining the existing state for organizations with no repositories.

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

Evaluación

Stack tecnológico
javascript
Área
frontend
Tipo de issue
Error
Dificultad
2/5
Tiempo estimado
1-3 horas
Estado de actividad
Activo
Claridad
Bien especificado
Aptitud para principiantes
86/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.