[FEATURE]: Add repository search/filter to the Overview page
Los mantenedores suelen responder en 1 día
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 20/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Estancado
- Stack tecnológico
- javascript, react
Línea de trabajo
Read src/pages/OverviewPage.jsx and compare the existing search inputs on GovernancePage.jsx and RepositoriesPage.jsx. The issue names the current topRepos calculation and the C.input style in src/components/UI.jsx; use those as entry points. Done means matching repository names appear as the query changes, the empty query keeps the top five, and an active query shows the result count. A linked open pull request (#409) indicates work is already underway.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Feature and its Use Cases
[FEATURE]: Add repository search/filter to the Overview page
Feature and its Use Cases
What is the feature?
The Overview page currently shows a hardcoded "High Impact Repositories" card with the top 5 repos sorted by health score. There is no way to search or filter across the full repository list from this page.
The feature adds a live search input above the "High Impact Repositories" card that filters totalRepos by repo name as the user types. The card would then display matching results instead of only the fixed top 5.
Current behavior
In src/pages/OverviewPage.jsx, topRepos is always computed as:
const topRepos = [...filteredRepos].sort((a, b) => b.healthScore - a.healthScore).slice(0, 5)
There is no user input — the list is always exactly 5 repos, always sorted by health score, with no way to look up a specific repo by name.
Proposed behavior
- A search input (text box) appears above the "High Impact Repositories" card
- As the user types,
topReposis filtered to repos whose name includes the query (case-insensitive) - When the search is empty, it falls back to the existing behaviour — top 5 by health score
- The result count is shown (e.g. "3 of 47 repos") when a query is active
How would users benefit?
- Organizations with many repos (50+) make the fixed top-5 view almost useless — users can't find specific repos without navigating away to the full Repositories page
- Users doing a quick check on a specific repo (e.g. "what is the health score of
my-api?") currently have no way to do that from the Overview - It reuses data already in memory (
totalRepos/filteredRepos) — zero extra API calls
Affected file
src/pages/OverviewPage.jsx— single file change, roughly 15–20 lines added
Proposed implementation sketch
// 1. Add state
const [repoSearch, setRepoSearch] = useState('')
// 2. Replace the hardcoded topRepos computation
const topRepos = repoSearch.trim()
? filteredRepos
.filter(r => r.name.toLowerCase().includes(repoSearch.trim().toLowerCase()))
.sort((a, b) => b.healthScore - a.healthScore)
.slice(0, 10)
: [...filteredRepos].sort((a, b) => b.healthScore - a.healthScore).slice(0, 5)
// 3. Add input above the card
<input
value={repoSearch}
onChange={e => setRepoSearch(e.target.value)}
placeholder="Search repositories..."
style={{ ...C.input, marginBottom: 12, width: '100%' }}
/>
Additional Context
- The
C.inputstyle object already exists insrc/components/UI.jsx— consistent styling is already available - The
filteredReposarray already respects the org filter dropdown (multi-org mode), so search will naturally scope to the selected org - Similar search inputs already exist on
GovernancePage.jsxandRepositoriesPage.jsx— this follows the same pattern used elsewhere in the codebase - No new dependencies needed
Additional Context
No response
Code of Conduct
- I have joined the Discord server and will post updates there
- I have searched existing issues to avoid duplicates
- Lenguaje dominante
- JavaScript
- Estrellas
- 53
- Forks
- 182
- Merge medio
- 18 min
- PR fusionados (30 d)
- 2
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de AOSSIE-Org/OrgExplorer
-
[BUG]: PAT popup input lacks label association and visibility button lacks an accessible namePosiblemente ocupada @prasanm1423 la tomó hace 3 días. Abiertobug enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
AOSSIE-Org/OrgExplorer#466 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
[FEATURE]: Set dynamic document.title based on active page routePosiblemente ocupada @23241a6749 la tomó hace 1 día. Abiertoenhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
AOSSIE-Org/OrgExplorer#462 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
[BUG]: SocialShareButton logs unconditional console.warn when script is not loadedPosiblemente ocupada @vivekrajputofficial29-afk la tomó hace 1 día. Abiertobug enhancement
Dificultad 1/5 Menos de una hora Aptitud para principiantes 89/100
AOSSIE-Org/OrgExplorer#461 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
[BUG]: governance page shows "No dead issues" before the audit has runQuizá libre de nuevo @SYED-IRTEZA-HUSSAIN-RIZVI la tomó hace 8 días y no hay ningún pull request abierto. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
AOSSIE-Org/OrgExplorer#453 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
[BUG]: User-controlled org/repo names are interpolated into API URLs unencodedPosiblemente ocupada @AbhishekKumar-cse la tomó hace 10 días. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
AOSSIE-Org/OrgExplorer#449 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de AOSSIE-Org/OrgExplorer
Issues similares
-
enhancement frontend good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 2 días
-
marketing
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
[bug]: Maximizing the Windows dashboard covers the taskbarPosiblemente ocupada @xiufengsun la tomó hoy. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 63/100
xiufengsun/TokenTracker#1152 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
parity: scripting.net's net-http row fails on macOS with errno 61 where the BDS golden has 111AbiertoBug Tests
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
JSPrismarine/JSPrismarine#3384 ·
Los mantenedores suelen responder en 1 día
-
cat:test dx effort:xs sev:low
Dificultad 1/5 1-3 horas Aptitud para principiantes 82/100
LucasSantana-Dev/Lucky#3251 ·
Los mantenedores suelen responder en 1 día