Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#4,045 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

@anth-volk já está trabalhando nisso.

Desde 26/10/2026.

  • #4046 de @anth-volk — aberto

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Estagnada
Stack de tecnologia
python
Domínio
api, backend, databases

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Python
Estrelas
18
Forks
33
Merge médio
2d 7h
PRs com merge (30d)
64

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de PolicyEngine/policyengine-api

Todas as issues de PolicyEngine/policyengine-api

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.