chore(lint): atualiza eslint baseline 1571→1547 (F1-1.x)#107
Merged
Conversation
24 erros eliminados nos PRs da Faxina F1 desta semana (Onda 1, #103, #104, #99, etc) que entraram em main como drift positivo. O `pre-push` hook já sugeria "Considere atualizar o baseline" desde a Onda 1. **Antes:** - baseline: 1571 erros - atual: 1547 erros (drift positivo de -24) **Depois:** - baseline: 1547 erros (congelados) - atual: 1547 erros (sem drift, sem regressão) **Distribuição dos 1547 erros congelados:** - 615 arquivos com pelo menos 1 violação ignorada - Maiores ofensores continuam sendo no-unused-vars, no-explicit-any, no-undef, eqeqeq (mesmas categorias mapeadas no relatório de auditoria — elas serão atacadas em PRs futuros da Fase 6) **Risk**: 🟢 zero. Apenas reduz o teto que o CI permite — torna o gate mais rigoroso, não menos. Qualquer regressão futura de lint vai falhar mais cedo. **Test plan**: - [x] `npm run lint:baseline:update` (regenerou) - [x] `npm run lint:baseline` (gate passa: atual=baseline=1547) - [ ] CI verde - [ ] CodeRabbit OK
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
WalkthroughAtualização do baseline de linting refletindo redução de 24 erros (1571 → 1547). Dois arquivos adicionados, sete removidos, e melhorias em arquivo existente. Timestamp atualizado para 2026-05-09. ChangesAtualização de Baseline de Linting
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related issues
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Pull request overview
Updates the repository’s ESLint baseline file to match the current lint error total (1547), tightening the CI “lint baseline” gate to prevent silent regressions as code gets cleaned up.
Changes:
- Regenerated
.eslint-baseline.jsonwith an updatedgeneratedAttimestamp. - Lowered
totalErrorsfrom 1571 → 1547 and updated per-file/rule counts accordingly.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
.eslint-baseline.json (1)
944-946: 🛠️ Refactor suggestion | 🟠 Major | ⚡ Quick winArquivo novo com 5 variáveis não utilizadas adicionado ao baseline
OnboardingTour.tsxestá sendo adicionado com 5 violações@typescript-eslint/no-unused-vars. Embora menos crítico queno-undef, ainda é questionável adicionar código novo com violações ao baseline.Recomendação: Limpar as variáveis não utilizadas neste arquivo antes de finalizar a atualização do baseline para manter a consistência com o objetivo da Faxina F1.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.eslint-baseline.json around lines 944 - 946, The new OnboardingTour component is added with five `@typescript-eslint/no-unused-vars` violations; fix this by opening src/components/onboarding/OnboardingTour.tsx, identify the unused variables (e.g., any unused props, state variables, helper functions or imported symbols) and either remove them, use them appropriately, or rename them with a leading underscore if intentionally unused; avoid adding exceptions to the baseline—ensure functions/classes like OnboardingTour and any unused imports are cleaned so the file has no `@typescript-eslint/no-unused-vars` violations before updating the baseline.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In @.eslint-baseline.json:
- Around line 944-946: The new OnboardingTour component is added with five
`@typescript-eslint/no-unused-vars` violations; fix this by opening
src/components/onboarding/OnboardingTour.tsx, identify the unused variables
(e.g., any unused props, state variables, helper functions or imported symbols)
and either remove them, use them appropriately, or rename them with a leading
underscore if intentionally unused; avoid adding exceptions to the
baseline—ensure functions/classes like OnboardingTour and any unused imports are
cleaned so the file has no `@typescript-eslint/no-unused-vars` violations before
updating the baseline.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 88bc0659-c448-4cb7-ab24-12d024da5f20
📒 Files selected for processing (1)
.eslint-baseline.json
5 tasks
This was referenced May 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Plano
Atualiza
.eslint-baseline.jsonpra refletir o estado atual do código (1547 erros) em vez do estado antigo (1571 erros).24 erros foram eliminados naturalmente durante os PRs da Faxina F1 desta semana — o pre-push hook já vinha sugerindo: "Drift positivo: 24 erro(s) eliminado(s). Considere atualizar o baseline."
Antes vs depois
Por que isso importa
O baseline funciona como teto rolling: o CI não falha se o número TOTAL de erros não exceder o baseline. Se o baseline for maior que o atual, ele permite regressões silenciosas (alguém adiciona 24 erros novos sem o CI reclamar — pq ainda não chega em 1571).
Atualizar trava o ganho desta semana e força os próximos PRs a manter ou melhorar.
Diff
Risk
🟢 Zero. O baseline só fica MAIS rigoroso — torna o gate menor, não maior. Não pode quebrar nada que já funcionava, só pode prevenir novas regressões.
Test plan
npm run lint:baseline:update(regenerou OK)npm run lint:baseline(gate passa: atual=baseline=1547)Summary by CodeRabbit
Notas de Lançamento
Nota: Esta versão contém apenas alterações internas de manutenção sem impacto direto nas funcionalidades visíveis ao usuário final.