AOSSIE-Org / AOSSIE-Org/OrgExplorer

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

オープン 初心者向け
#193 コメント 4 件 リアクション 0 件 担当者 0 名 GitHub で見る
bug
主要言語
JavaScript
スター
34
フォーク
92
平均マージ
8日 7時間
マージ済み PR(30日)
12

説明

### 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

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

評価

技術スタック
javascript
領域
frontend
issue の種類
バグ
難易度
2/5
見積もり時間
1〜3時間
活発さ
活発
明瞭さ
明確に書かれている
初心者へのやさしさ
86/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。