PolicyEngine / PolicyEngine/policyengine-app-v2

Standardize ingredient-creation action labels

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

Nobody has claimed this yet.

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

Description

Equivalent stages of policy, population, simulation, and report creation currently mix labels such as “Add,” “Configure,” and “Create.”

Define and apply one terminology mapping across the pathways and report builder:

  • Entry action: “Set up [ingredient]”
  • Intermediate action that opens or continues configuration: use the same “Set up” wording unless it performs a distinct operation
  • Final persistence action: “Create [ingredient]”
  • Existing-record changes: “Save” or “Update,” according to the actual operation

Update relevant tests and stories with the chosen labels.

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

Search the policy, population, simulation, and report-creation pathways, including the report builder, to find the current action labels. Then update the relevant tests and stories to use the specified distinction between setup, creation, saving, and updating, and verify that all listed flows use consistent wording.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
frontend, testing
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.