PolicyEngine / PolicyEngine/policyengine-app-v2
Disable congressional district impact map in US report outputs
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1
- Forks
- 3
- Avg merge
- 1d 50m
- Merged PRs (30d)
- 39
Description
Summary
Disable the congressional district impact map (CongressionalDistrictCard) in US report outputs. It renders on every US report via MigrationSubPage.tsx → CongressionalDistrictDataProvider, and is gated only on US + reform + baseline + year (not on the report's geography).
Constraint
Previously created reports must remain fully viewable. Because the map is recomputed live on view (never stored per-report), hiding it does not affect the ability to open/render existing reports — they simply no longer show the map.
Decision
Hide it everywhere (not only for newly created reports). Gate the card off and drop the live-fetch provider so neither the map nor its data request runs.
Contributor guide
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 in MigrationSubPage.tsx and trace the CongressionalDistrictDataProvider and CongressionalDistrictCard references. Disable the card and remove its live-fetch provider so US report outputs make no map request, while previously created reports still open and render without the map.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100