Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Serve economy reports on the v2 routes and save v2 report and simulation IDs

Offen
  • Stimmt etwas nicht?
#4,107 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

@anth-volk arbeitet bereits daran.

Seit 28.10.2026.

  • #4108 von @anth-volk — offen

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
python
Bereich
api, backend

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Python
Sterne
18
Forks
33
Ø Merge
2 T. 7 Std.
Gemergte PRs (30 T.)
64

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus PolicyEngine/policyengine-api

Alle Issues in PolicyEngine/policyengine-api

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.