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

Ambiguous tax ranges in Part 2:Gift tax calculator exercise. Specify inclusive/exclusive boundaries

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

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript
Domain
documentation

Research direction

Start with the Part 2: Gift tax calculator exercise description and compare its stated value ranges with the solution's boundary notation. Clarify whether each boundary is inclusive or exclusive, then run the existing test code to confirm the documented ranges remain consistent.

Written by the indexing model from the issue text.

Description

In Part 2 : Gift tax calculator exercise the boundaries of value ranges are ambigious. This part of the problem description "If the total value of the gifts you receive from the same donor in the course of 3 years is €5,000 or more, you must pay gift tax." implies that the first boundary is inclusive and the second is exclusive (since the second boundary is repeated as the frst one in the following ranges so that must be exclusive : ex: (50 - 100] ). But the solution of the exercise has used second boundary as the inclusive boundary rather than the first one (ex: [50 - 100)). The test code works fine in both cases but the clarity can be improved throug clear indication of the ranges ( either (50-100] or [50 - 100] ).

Dominant language
JavaScript
Stars
81
Forks
29
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No 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 rage/programming-26

All issues in rage/programming-26

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.