Use British spelling for UK LSR parameter paths#2829
Use British spelling for UK LSR parameter paths#2829vahid-ahmadi wants to merge 1 commit intomainfrom
Conversation
The UK labour supply response parameters are being renamed from gov.simulation.labor_supply_responses.* to gov.simulation.labour_supply_responses.* in PolicyEngine/policyengine-uk#1607. Update the two UK-only path strings in PolicyRightSidebar so the LSR sliders keep resolving after that merges. US paths unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Pull request overview
Updates the PolicyRightSidebar’s UK behavioral response parameter paths to align with the upstream policyengine-uk rename from labor_supply_responses to labour_supply_responses, keeping the UK LSR toggle/sliders functional after the backend change.
Changes:
- Renamed two UK parameter path strings in
BehavioralResponseToggleto uselabour_supply_responses. - Added a changelog entry documenting the UK LSR path rename.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| src/pages/policy/PolicyRightSidebar.jsx | Switches UK behavioral-response reform keys to labour_supply_responses.* so UK LSR toggles target the renamed parameters. |
| changelog_entry.yaml | Notes the UK LSR parameter path update for release tracking. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "gov.simulation.labour_supply_responses.income_elasticity": { | ||
| [dateString]: -0.05, | ||
| }, | ||
| "gov.simulation.labor_supply_responses.substitution_elasticity": { | ||
| "gov.simulation.labour_supply_responses.substitution_elasticity": { | ||
| [dateString]: 0.25, |
Mirror the two consumed paths (`income_elasticity` and `substitution_elasticity`) under the renamed `labour_supply_responses` tree back to `gov.simulation.labor_supply_responses.*`, so the legacy policyengine-app PolicyRightSidebar (which hard-codes the old paths) keeps working between this PR landing and the matching app PR rebuilding against the new path. Removes the merge-window breakage that would otherwise hit the LSR sliders. Remove this alias in a follow-up release once consumers (the app PR PolicyEngine/policyengine-app#2829) have migrated. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* Rename labor to labour in LSR parameters and variables Use British English spelling throughout the labour supply response module: directory names, file names, parameter labels, descriptions, import paths, and test references. Fixes #853. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Remove unrelated EASY_ISSUES file * Add deprecation alias for legacy labor_supply_responses paths Mirror the two consumed paths (`income_elasticity` and `substitution_elasticity`) under the renamed `labour_supply_responses` tree back to `gov.simulation.labor_supply_responses.*`, so the legacy policyengine-app PolicyRightSidebar (which hard-codes the old paths) keeps working between this PR landing and the matching app PR rebuilding against the new path. Removes the merge-window breakage that would otherwise hit the LSR sliders. Remove this alias in a follow-up release once consumers (the app PR PolicyEngine/policyengine-app#2829) have migrated. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * Map legacy LSR parameter changes --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: Max Ghenis <mghenis@gmail.com>
|
I reviewed this after merging PolicyEngine/policyengine-uk#1607. I am leaving the app PR unmerged for now because the frontend would start sending the new |
Summary
gov.simulation.labor_supply_responses.*→gov.simulation.labour_supply_responses.*in the UK repo.PolicyRightSidebar.jsx(income_elasticity,substitution_elasticity) so the LSR sliders keep resolving after the UK rename lands.elasticities.*) are untouched — those live inpolicyengine-usand aren't being renamed.Coordination
Merge order matters: this PR should land immediately before or after policyengine-uk#1607 to minimize the window where one side disagrees with the other. Safer sequence:
policyengine-ukin the app.Test plan
🤖 Generated with Claude Code