Serve economy reports on the v2 routes and save v2 report and simulation IDs
维护者通常 2 天内回复
评估
调研方向
Start with the existing Public API v2 routes for saved reports and simulations, then read the simulation service routes that create, run, and read economy reports and simulations. Trace how country settings are checked before service calls and how saved IDs are validated. Done means the v2 economy report routes support the listed read, submit, list, rerun, and run-history operations, reject household-only countries with a 422 before calling the service, and accept validated v2 IDs for saved records.
由索引模型根据 Issue 内容生成。
描述
The Public API's v2 routes can save a user's reports and simulations, but only as references to v1 records, and there is no v2 route that calculates or reads an economy (society-wide) report. The simulation service is gaining routes that create, run and read economy reports and their simulations in its own database.
This adds /v2/reports for economy reports on top of those routes: submit a report, read it (by ID or by the v1 report number it was migrated from), list chosen reports, run it again on the current catalog version (optionally recalculating both simulations), and list its runs with the versions each used. A report migrated from v1 has no run, so it is calculated the first time it is read.
It also lets saved reports and saved simulations hold the v2 IDs of those records, checked with the simulation service before they are saved, since the tables keep no foreign key to another service's database.
A country whose countries row does not allow society-wide calculations (a household-only country) must be refused with a 422 naming it, before anything is sent to the simulation service.
Nothing in the app calls these routes yet.
- 主要语言
- Python
- 星标
- 18
- 派生
- 33
- 平均合并
- 2 天 7 小时
- 30 天内合并 PR
- 64
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
PolicyEngine/policyengine-api 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
PolicyEngine/policyengine-api#4037 ·
维护者通常 2 天内回复
-
难度 1/5 1-3 小时 新手友好度 88/100
PolicyEngine/policyengine-api#3911 ·
维护者通常 2 天内回复
-
难度 1/5 1 小时以内 新手友好度 82/100
PolicyEngine/policyengine-api#3910 ·
维护者通常 2 天内回复
-
Split the release tests over six runners, and stop repeating the merge run's checks on the release commit可能已有人在做 @anth-volk 今天认领。 未关闭
难度 4/5 3-5 天 新手友好度 25/100
PolicyEngine/policyengine-api#4133 ·
维护者通常 2 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
PolicyEngine/policyengine-api#4131 ·
维护者通常 2 天内回复
查看 PolicyEngine/policyengine-api 的全部 Issue
相似的 Issue
-
Support .aac audio uploads可能已有人在做 @julien731 今天认领。 未关闭feature
难度 2/5 1-3 小时 新手友好度 78/100
nimblehq/audio-transcriber#153 ·
-
help wanted
难度 2/5 1-3 小时 新手友好度 68/100
antonyrag/ragleap-core#1062 ·
-
needs-triage
难度 2/5 1-3 小时 新手友好度 76/100
gke-labs/kube-agents#4321 ·
维护者通常 1 天内回复
-
enhancement help wanted
难度 2/5 1-3 小时 新手友好度 76/100
Git-Hospital/githealthcheck#61 ·
维护者通常 1 天内回复
-
changelog investigate
难度 2/5 1-3 小时 新手友好度 67/100
ramnes/notion-sdk-py#433 ·