[V1-1] Checklist de paridade completa
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- javascript, node.js
- Domain
- backend
Research direction
Read section 10's parity table in ZAPFORGE_PLAN.md, along with the v1.0 Virada reference in section 9, then compare each legacy capability with the work in apps/lumabot. The issue does not identify specific files or tests, so first map the table items to the relevant code. Done means every row in the table is checked and the general DoD is met.
Written by the indexing model from the issue text.
Description
Bridger · #V1-1 · Milestone v1.0 Virada · Pacote
apps/lumabot
Objetivo
Confirmar que tudo que o legacy faz existe no Bridger (seção 10).
Critérios de aceite
- Todas as linhas da tabela da seção 10 marcadas
DoD geral
Testes verdes; nenhum teste existente apagado/reescrito sem autorização; docs (COMO) atualizadas; ADR quando houver decisão arquitetural; changeset criado; Biome sem erros; benchmark sem regressão > 10% (a partir do M2).
Decisões relacionadas
- D23: Migração incremental (legacy/)
- Tabela completa: BRIDGER_PLAN.md §4
Referência
- Dominant language
- JavaScript
- Stars
- 26
- Forks
- 6
- Avg merge
- 43m
- Merged PRs (30d)
- 137
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from murillous/LumaBot
-
area:plugin type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:plugin good first issue type:bug
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
area:plugin good first issue type:debt
Difficulty 3/5 1-2 days Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:plugin type:bug
Difficulty 3/5 1-2 days Newbie friendliness 54/100
Maintainers usually reply within 1 day
-
area:plugin type:feature
Difficulty 4/5 1-2 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
All issues in murillous/LumaBot
Similar issues
-
correction via-web
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
ch-bas/cctv-camera-database#416 ·
Maintainers usually reply within 1 day
-
bug effort:medium model:light tests
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
piskyRpapalo/preceptoros-web#231 ·
Maintainers usually reply within 1 day
-
type/bug type/docs type/enhancement
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Redo-San/RedoSan-Authenticity#574 ·
Maintainers usually reply within 1 day
-
Place search spins forever when nominatim failsPossibly taken @jgt87 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
anvaka/city-roads#213 ·