Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Serve the v2 parameter tree one level at a time from a tree written with each catalog version

Ouverte
  • Quelque chose ne va pas ?
#4,045 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

@anth-volk y travaille déjà.

Depuis le 26/10/2026.

  • #4046 par @anth-volk — ouverte

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
À l'abandon
Stack technique
python
Domaine
api, backend, databases

Piste de recherche

Start by reading the v2 /parameters/children route and the catalog version publishing path; the issue does not name their files or tests. Trace how parameter nodes and bracket schedules are represented, then identify where catalog rows are written and read. Done means an indexed read serves one ordered level, bracket schedules appear as nodes with labelled brackets, and reform filtering and child counts match the requested rules.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

The app's newer workspace (v3) is moving from the Public API's /{country}/metadata to the v2 metadata routes, and it browses its parameter tree one level at a time through /v2/parameters/children. That route cannot serve it today:

  • It is slow. It finds a level's children by scanning every parameter and node name under the path on each request. Measured in production on 2026-10-21, a level takes 2.7–6.1 s.
  • Bracket schedules are wrong. Brackets such as gov.hmrc.income_tax.rates.uk[0] are listed beside their parent's real groups, under their raw names. The schedule itself (uk) is missing, or is listed with no children.
  • It cannot show only what a reform can change. v3's tree keeps only parameters whose economy or household flag is set, and leaves out taxsim and gov.abolitions. The route has no way to apply those rules.

What should change

  • Publishing a catalog version writes each node's direct children, in order, to a table. Each row holds the child's label, its child counts, and whether a reform can change it.
  • A bracket schedule is one node whose children are its brackets, labelled "Bracket 1", "Bracket 2" and so on.
  • The route reads one level with one indexed read. On request, it lists only what a reform can change, sorted by label, with child counts to match.

Paths, parameter IDs and values stay the same. v3 does not use the route until it moves to the v2 routes.

Langage dominant
Python
Étoiles
18
Forks
33
Merge moyen
2 j 13 h
PR mergées (30 j)
56

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de PolicyEngine/policyengine-api

Toutes les issues de PolicyEngine/policyengine-api

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.