Store the metadata v3 reads in the v2 catalog, from PolicyEngine.py's public records
维护者通常 3 天内回复
评估
调研方向
Start with the catalog publishing code and its format 2 records, then inspect PolicyEngine.py's public records at PolicyEngine/policyengine.py#701 and the /{country}/metadata route. Compare the metadata for the US and UK to check every new field, and review how earlier catalog versions leave those fields empty. Done means the published catalog matches both routes and the Public API uses a PolicyEngine.py release that provides the fields.
由索引模型根据 Issue 内容生成。
描述
The app's newer workspace (v3) reads several metadata fields from /{country}/metadata that the v2 catalog does not store: each model's entities (key, plural name, whether it is the person entity) and basic inputs (the household builder's default fields); each variable's input and hidden-input flags, its module, the parameter that names what it adds or subtracts, and the labels of its enum values; each parameter's economy and household flags; and bracket schedules as nodes of the parameter tree with their labels.
Without these fields, v3 cannot load its metadata from the v2 routes. PolicyEngine.py now publishes them in its public records (PolicyEngine/policyengine.py#701), so the catalog can take them from there instead of from the country package's tax-benefit system or a private PolicyEngine.py method.
What is needed:
- Store the fields when a catalog version is published (catalog format 2), read only from PolicyEngine.py's public records.
- Keep catalog versions published earlier unchanged: their new fields stay empty.
- Check each new field against what
/{country}/metadatapublishes for the US and the UK. - Move the Public API's PolicyEngine.py dependency to the release that publishes the fields.
- 主要语言
- Python
- 星标
- 18
- 派生
- 33
- 平均合并
- 2 天 18 小时
- 30 天内合并 PR
- 36
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
PolicyEngine/policyengine-api 的其他 Issue
-
难度 1/5 1-3 小时 新手友好度 88/100
PolicyEngine/policyengine-api#3911 ·
维护者通常 3 天内回复
-
难度 1/5 1 小时以内 新手友好度 82/100
PolicyEngine/policyengine-api#3910 ·
维护者通常 3 天内回复
-
Stop serving economy results cached with ×100 decile relative changes可能已有人在做 @anth-volk 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 45/100
PolicyEngine/policyengine-api#4025 ·
维护者通常 3 天内回复
-
Request UK constituency and local-authority impacts separately from the national economy result可能已有人在做 @anth-volk 今天认领。 未关闭
难度 4/5 3-5 天 新手友好度 25/100
PolicyEngine/policyengine-api#4021 ·
维护者通常 3 天内回复
-
Publish v2 catalog regions from the Public API's own region reference files可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 5/5 一周以上 新手友好度 38/100
PolicyEngine/policyengine-api#4019 ·
维护者通常 3 天内回复
查看 PolicyEngine/policyengine-api 的全部 Issue
相似的 Issue
-
难度 1/5 1-3 小时 新手友好度 88/100
fossasia/visdom-dev#69 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
BUG: PROD: v1.3.0-beta Onboarding Profile Picture Misaligns When Name Validation Error Appears可能已有人在做 @RitikaSen27 今天认领。 未关闭bug good first issue
难度 2/5 1-3 小时 新手友好度 82/100
AOSSIE-Org/PictoPy#1647 · 2 条评论 ·
维护者通常 2 天内回复
-
[oblt-aw][autodoc] Update workflow docs for gh-aw v0.92.5 and detector permission scope可能已有人在做 @github-actions 今天认领。 未关闭
难度 1/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复