[FEATURE]: Add repository search/filter to the Overview page
I maintainer di solito rispondono entro 1 giorno
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 20/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Ferma
- Stack tecnologico
- javascript, react
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
- Lingua principale
- JavaScript
- Stelle
- 53
- Fork
- 182
- Merge medio
- 18m
- PR unite (30g)
- 2
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di AOSSIE-Org/OrgExplorer
-
[BUG]: PAT popup input lacks label association and visibility button lacks an accessible nameForse già presa @prasanm1423 l’ha presa 3 giorni fa. Apertabug enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
AOSSIE-Org/OrgExplorer#466 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
[FEATURE]: Set dynamic document.title based on active page routeForse già presa @23241a6749 l’ha presa 1 giorno fa. Apertaenhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
AOSSIE-Org/OrgExplorer#462 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
[BUG]: SocialShareButton logs unconditional console.warn when script is not loadedForse già presa @vivekrajputofficial29-afk l’ha presa 1 giorno fa. Apertabug enhancement
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 89/100
AOSSIE-Org/OrgExplorer#461 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
[BUG]: governance page shows "No dead issues" before the audit has runForse di nuovo libera @SYED-IRTEZA-HUSSAIN-RIZVI l’ha presa 8 giorni fa e non c’è nessuna pull request aperta. Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
AOSSIE-Org/OrgExplorer#453 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
[BUG]: User-controlled org/repo names are interpolated into API URLs unencodedForse già presa @AbhishekKumar-cse l’ha presa 10 giorni fa. Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
AOSSIE-Org/OrgExplorer#449 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di AOSSIE-Org/OrgExplorer
Issue simili
-
marketing
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
[bug]: Maximizing the Windows dashboard covers the taskbarForse già presa @xiufengsun l’ha presa oggi. Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 63/100
xiufengsun/TokenTracker#1152 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
parity: scripting.net's net-http row fails on macOS with errno 61 where the BDS golden has 111ApertaBug Tests
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
JSPrismarine/JSPrismarine#3384 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
desec-io/desec-stack#1312 ·
I maintainer di solito rispondono entro 14 giorni
-
Difficoltà 1/5 1-3 ore Idoneità per principianti 72/100
w3c/csswg-drafts#14848 ·
I maintainer di solito rispondono entro 1 giorno