PolicyEngine / PolicyEngine/policyengine-api
Refactor Metadata Handling to Avoid Duplication Between Backend and Frontend
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 33
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 22
Description
We're currently using the country ID to fetch the metadata from the backend, then merging the retrieved response, manipulating certain fields, and appending country-specific details using country ID. Metadata is being constructed in both backend and frontend. https://github.com/PolicyEngine/policyengine-api/issues/2031
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
Read the related issue 2031, then trace how the backend fetches metadata by country ID and how the frontend merges and modifies that response. The work is done when metadata construction has a single clear source instead of being duplicated across backend and frontend, with country-specific details still handled consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100