PolicyEngine / PolicyEngine/policyengine-core
Formalise references
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 22
- Forks
- 30
- Avg merge
- 14h 33m
- Merged PRs (30d)
- 7
Description
Currently, references are a union of different formats: strings, tuples and lists. We should define a concrete Reference class, with a defined JSON translation, to make detailed references machine-friendly.
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 named. Start by locating where references are represented as strings, tuples, and lists, then trace their JSON translation. Done means a concrete Reference class replaces the mixed formats and supports a defined, machine-friendly JSON representation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100