runceel / runceel/lets-learn-githubcopilot-app-20260824

Add a search box to find games by title

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
2m
Merged PRs (30d)
2

Description

Players who already know what they're looking for shouldn't have to scan the whole catalog. Adding a simple search box on the game list page lets users quickly narrow the list by title, improving discoverability alongside the planned category and publisher filters. This builds on the existing game list data layer without changing the data model.

Acceptance criteria

  • The game list page includes a search input that filters games by title
  • Matching is case-insensitive and updates the visible list as the user types or submits
  • An appropriate empty state is shown when no games match the search
  • The search input follows the project's accessibility guidelines (labeling, keyboard navigation, visible focus states) and includes a data-testid attribute
  • Unit tests cover any new data-layer/search helper and Playwright e2e tests cover the search behavior

Contributor guide

Open the contributing guide

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.

Research direction

Start at the game list page and its existing game list data layer, then trace how the visible game collection is rendered. Add the title search behavior, accessible input, empty state, and data-testid described in the acceptance criteria. Run the relevant unit tests and add or run Playwright coverage for typing or submitting a search and displaying matching and empty results.

Written by the indexing model from the issue text.

Assessment

Tech stack
playwright, typescript
Domain
frontend, testing
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
74/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.