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

Add proper date checks for contracts.

Open
#412 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
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

No file, test, or entry point is named. Start by locating the backend contract validation and its existing date-handling tests, then verify how invalid dates are reported. Done means start dates accept only the 1st or 16th and end dates accept only the 15th or the month's last day.

Written by the indexing model from the issue text.

Description

enhancement

For contracts following checks should be added in backend.

  • start date: only the 1st or 16th of a month

  • end dates: only the 15th or last day of a month

Dominant language
Python
Stars
0
Forks
4
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 ClockGU/clock-backend

All issues in ClockGU/clock-backend

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.