github-samples / github-samples/tailspin-toys

Allow users to filter games by category and publisher

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

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
8
Forks
53
Avg merge
20h 1m
Merged PRs (30d)
4

Description

As the game catalog grows, players need a faster way to find titles relevant to them. Adding the ability to filter the game list by category and by publisher improves discoverability and directly supports the platform's goal of helping backers find games to support. The data model already includes categories and publishers, so this builds on existing structures.

Acceptance criteria

  • Users can filter the game list by one or more categories
  • Users can filter the game list by publisher
  • Category and publisher filters can be combined
  • The data-access helpers in src/lib/ support filtering games by category and publisher
  • Filter controls follow the project's accessibility guidelines (keyboard navigation, ARIA, visible focus states) and include data-testid attributes
  • Vitest unit tests cover the filtering helpers and Playwright e2e tests cover the new filtering 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 by locating the existing game-list UI and the data-access helpers in src/lib/, then review the current Vitest and Playwright test setup. Add combined category and publisher filtering with accessible controls and data-testid attributes; done means the acceptance criteria pass, including unit coverage for helpers and end-to-end coverage of filtering behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
playwright, typescript
Domain
accessibility, full-stack, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.