Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#4,045 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

@anth-volk ya está trabajando en esto.

Desde el 26/10/2026.

  • #4046 de @anth-volk — abierto

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
python
Área
api, backend, databases

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
18
Forks
33
Merge medio
2 d 7 h
PR fusionados (30 d)
64

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de PolicyEngine/policyengine-api

Todos los issues de PolicyEngine/policyengine-api

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.