PolicyEngine / PolicyEngine/policyengine-core
Support amount_unit instead of rate_unit for amount scale parameters
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 22
- Forks
- 30
- Avg merge
- 14h 33m
- Merged PRs (30d)
- 7
Description
Claude and I just got confused by the requirement to use rate_unit instead of amount_unit for scale parameters that specify amounts.
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
No files, tests, or entry points are mentioned. Start by locating the handling and validation of scale parameters, then inspect existing tests for rate_unit usage. Done means amount_unit is supported for parameters that specify amounts, with the existing behavior for rate_unit preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100