Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Language Filter Dropdown Silently Truncates Languages

Open Beginner friendly
#289 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@PrithvijitBose is already working on this.

Since Oct 2, 2026.

  • #290 by @PrithvijitBose — open

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
85/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

Open RepositoryPage.jsx and inspect how the language list is built from allRepos, especially the .slice(0, 10) call and the 'All Languages' entry. Verify the dropdown with an organization containing more than nine languages. Done means every distinct repository language is available for filtering, including languages encountered later in the repository list.

Written by the indexing model from the issue text.

Description

bug

In RepositoryPage.jsx

Image
What Exactly Goes Wrong?
  1. Only 9 Languages Can Ever Exist in the Dropdown:
  • Index 0 of the array is 'All Languages'.
  • The .slice(0, 10) restricts the total array length to 10 elements.
  • That means only 9 unique programming languages are ever allowed into the dropdown.
  • If an organization has 10, 15, or 25 languages across its repositories, every language after the 9th is silently dropped.
  1. Arbitrary Insertion Order (Not Even Popularity-Based):
  • new Set(...) preserves the order in which items are first encountered in allRepos.
  • So whichever 9 languages happened to appear first in the API response fill up the 9 slots.
  • A repository with 5,000 stars written in Go or Rust might have its language completely omitted from the filter if it - appeared further down in the list!

Example

If you visit Adobe's Org

Image

You will not Find "Python" although it was updated few hours ago

Image
Dominant language
JavaScript
Stars
42
Forks
124
Avg merge
2d 22h
Merged PRs (30d)
10

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AOSSIE-Org/OrgExplorer

All issues in AOSSIE-Org/OrgExplorer

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.