PolicyEngine / PolicyEngine/policyengine-app-v2

Allow editing baseline/reform policy from report output page

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

Nobody has claimed this yet.

Dominant language
HTML
Stars
1
Forks
3
Avg merge
1d 50m
Merged PRs (30d)
39

Description

Context

User feedback from Greg Miller (Land Economics) while using the report output view.

Problem

After a report is generated, there's no easy way to modify the baseline or reform policy from the report output page. Users who want to tweak parameters must start the entire report creation flow from scratch.

Greg's feedback: "from Reports, or an existing Report, it'd be great if there were an easy way to modify the baseline and treatment policy."

Suggested behavior

On the report output page, add edit actions (e.g., pencil icons or "Edit" links) next to the baseline and reform simulation summaries that allow users to:

  1. Modify the policy parameters of either simulation
  2. Re-run the report with the updated configuration
  3. Optionally save as a new report variant

UX questions to discuss

  • Should edits create a new report or update the existing one?
  • Should this be a full re-entry into the pathway, or an inline parameter editor?
  • How to handle the case where the user changes population scope (not just policy)?

Files

  • app/src/pages/ReportOutput.page.tsx
  • Report metadata display components

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 with app/src/pages/ReportOutput.page.tsx and the report metadata display components to understand how baseline and reform simulations are shown. Review the existing report creation flow before deciding whether editing re-enters that pathway or uses an inline editor. Done means users can modify either policy from the output page, rerun the report, and have the save-as-new-variant behavior resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.