Implementation allows for invalid month + day combinations
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6
- Forks
- 6
- Avg merge
- 8d 10h
- Merged PRs (30d)
- 4
Description
e.g., we permit a month value of B (February) to be paired with a day value of d (29) in a non-leap year situation.
A truly complete solution would account for the Cask-legal leap years between 2028 - 2088.
We do not have a timestamp range that requires handling a 'century' leap year'.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating month-and-day validation in the C# reference API and its tests, then reproduce the February 29 case in a non-leap year. Done means invalid month/day combinations are rejected, Cask-legal leap years from 2028 through 2088 are handled, and century leap years remain out of scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100