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

[Time Between Classes] Bind the minimum-gap input

Open Beginner friendly
#784 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
86/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Domain
frontend

Research direction

Read src/components/plans/CreatePlanDialog.tsx, especially the Filters fieldset, credit-hour inputs, and the getRecommendedSchedules({...}) call. Keep the new optional values in dialog state and pass them as minGapMinutes and maxGapMinutes; show an inline message and prevent generation when the minimum exceeds the maximum. Check the acceptance cases and run pnpm lint, pnpm typecheck, and pnpm test.

Written by the indexing model from the issue text.

Description

Frontend time-gaps

What to build

Add the minimum “time between classes” field to the create-plan form. Send the entered number of minutes to schedule generation, and leave the setting unset when the field is empty.

Files

Steps

  1. Add a string state for the optional minutes field and a labelled number input in the Filters fieldset.
  2. Follow the existing credit-hour markup; empty text maps to omission, not 0. On submit add the parsed number to getRecommendedSchedules input.
  3. Keep state local to the dialog; do not persist preferences in this slice.

Example

Shortest input 15/90 → matching numeric action key; empty → no key.

Check it works

In src/components/plans/CreatePlanDialog.test.tsx, check the example above and the failure or limit described in the steps. Run pnpm test -- src/components/plans/CreatePlanDialog.test.tsx, pnpm lint and pnpm typecheck.

References

Assign yourself before starting, or comment to claim the issue. Project setup.

Dominant language
TypeScript
Stars
19
Forks
94
PR merge metrics
No merged PRs in 30d

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 DevDogsUGA/DogDays

All issues in DevDogsUGA/DogDays

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.