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

Past deadlines labelled "today"; search placeholder ignores eligibility filter

Open
#118 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Aryan-Techie is already working on this.

Since Oct 22, 2026.

  • #122 by @Aryan-Techie — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
typescript
Domain
frontend

Research direction

The report names the /deadlines and /directory routes but no files or tests. Start by locating those pages and the deadline label and search placeholder logic. Reproduce both cases from the listed steps; done when past deadlines show a closed label and the placeholder count matches the eligible offers. Pull request #122 is already open against this issue.

Written by the indexing model from the issue text.

Description

Route

/deadlines and /directory.

Steps to reproduce

Deadline label

  1. Open /deadlines less than 24 hours after a listed deadline has passed. For example, the Commonwealth Master's Scholarship closed on 20 Oct 2026; open the page on 21 Oct.
  2. Find that program in the past-cycles list.

Search placeholder

  1. Open /directory.
  2. Turn on "Only what I'm eligible for" and save an eligibility profile, e.g. India with only ".edu email" checked.
  3. Read the search box placeholder.

Actual behavior

  • The past program reads "Deadline Oct 20, 2026 · today", which looks like it's still open.
  • The placeholder still says "Search N offers…" with the unfiltered total, though fewer offers are shown.

Expected behavior

  • A deadline that has passed never reads as "today". Use something like "closed yesterday".
  • The placeholder reflects the number of offers actually being searched.
Dominant language
TypeScript
Stars
1
Forks
6
Avg merge
22h 9m
Merged PRs (30d)
42

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 Your-Voldemort/StudentStack

All issues in Your-Voldemort/StudentStack

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.