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

1-hour workshop: Include the page data owner in the filter exercise context

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
documentation

Research direction

Start with content/1-hour/4-add-feature.md, then read app/client/src/pages/index.astro, app/client/src/components/DogList.astro, and app/server/app.py to distinguish request, filtering, pagination, and presentation responsibilities. Validate the workshop from a fresh template copy; done means Step 4 names the page file, explains the query flow, and documents how pagination behaves when filters change.

Written by the indexing model from the issue text.

Description

priority: P1

Problem

Step 4 asks learners to add only app/server/app.py and app/client/src/components/DogList.astro to Copilot Edits. However, app/client/src/pages/index.astro owns the /api/dogs request, reads URL query parameters, and renders pagination. DogList.astro only receives and renders a dogs prop.

Without the page file in context, Copilot can produce a partial client-side filter or miss the request and pagination changes needed for the documented server-side filtering flow.

Suggested change

Update content/1-hour/4-add-feature.md to include app/client/src/pages/index.astro in the required context and explain at a high level which file owns the API request versus presentation.

Acceptance criteria

  • Step 4 includes app/client/src/pages/index.astro in the files supplied to Copilot.
  • The expected flow from filter controls to URL/API query parameters is stated.
  • Existing pagination parameters are preserved, or the page is deliberately reset, when filters change.
  • The exercise is validated from a fresh template copy.
Dominant language
Python
Stars
80
Forks
161
Avg merge
31m
Merged PRs (30d)
1

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.

More from github-samples/pets-workshop

All issues in github-samples/pets-workshop

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.