PolicyEngine / PolicyEngine/ccdf-calculator

Mark New Mexico cutoff percentages as lower bounds when the income grid is exhausted

Open
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

On Compare states with the default reference household (one adult, ages 3 and 7, $1,500/month per child), New Mexico shows:

  • Income cutoff: “Above $200,000”.
  • Cutoff as share of poverty line: 732%.
  • Cutoff as share of state median income: 271%.

The dollar column correctly recognizes that the model still pays at the top of the tested income range. The percentage columns nevertheless format that boundary as a finite cutoff. Neither percentage is an established income limit.

Propagate cutoffBeyondAxis to the percentage cells, map/ranking labels, and tooltips. Show “Above 732%” / “Above 271%” (with appropriate rounding) or a clear unavailable/unbounded label. Do not infer an unlimited policy solely from exhausting this grid. Add a regression that all representations of a censored cutoff remain consistent.

Source: src/components/ComparisonTable.tsx.

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.

Research direction

Start in src/components/ComparisonTable.tsx at the cutoff handling around the cited line, then trace cutoffBeyondAxis through the percentage cells, map and ranking labels, and tooltips. Add a regression covering every representation of a censored cutoff and verify that the displayed percentage values consistently use an above-bound or unavailable label.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs, typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.