fix(i18n): traduz toasts e completa chaves ES do menu - #744
Conversation
Toasts da esquina e vários hooks ignoravam t()/traduzir mesmo com entradas no dicionário; o NAV/hub também caía em português por chaves ausentes. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Someone is attempting to deploy a commit to the rafael-maudibrasil's projects Team on Vercel. A member of the Team first needs to authorize it. |
ECC Tools / Security EvidenceCommit: Security scanner evidence required (action_required) Detected 1 security-sensitive predictive risk signal(s) without scanner evidence. Mode: enforce Findings:
Touched security-sensitive paths:
Expected evidence:
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / PR Risk TaxonomyCommit: PR taxonomy review recommended (neutral) Detected 2 PR taxonomy bucket(s): Security Evidence, CI/CD Recommendation. Scanned 10 changed file(s). Roadmap taxonomy buckets: Security EvidenceSecurity-sensitive changes should carry explicit scanner, code-scanning, or focused regression evidence. Signals:
Paths:
CI/CD RecommendationCI, dependency, coverage, and contract signals should be routed into follow-up checks or verification work. Signals:
Paths:
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / Reference Set ReadinessCommit: Reference set readiness gaps detected (neutral) Reference evidence present for 0/7 areas (0%) across 10 changed file(s). This check is based on files changed in this PR. Repository-level readiness is still reported by
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / Hosted Promotion ReadinessCommit: Hosted promotion readiness passed (success) No hosted promotion evidence gaps detected across 10 changed file(s); 0 corpus scenarios had matching evidence. This check compares PR file changes against the evaluator/RAG promotion corpus in No evaluator corpus scenarios matched this PR. Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
|
Recebido, @biopaul — obrigado por isto. Duas coisas que vão parecer erro seu e não são:
Um mantenedor vai revisar de verdade — rodando os gates e reproduzindo o comportamento, não só Esta mensagem é automática e não diz nada sobre o seu PR: ela é sobre o processo. O que vem |
ECC Tools / PR Config AuditCommit: No changed-config issues detected (success) Scanned 3 config file(s) present at this commit across 3 changed config path(s) and found no issues in the supported security rules. Changed config files:
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / PR Harness AuditCommit: No harness issues detected (success) Scanned 3 changed config file(s) and found no harness issues. Changed config files:
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
Sem locale o NavHub caía em pt-BR e o hub inteiro ficava em português mesmo com idioma=es. Alinha ao CRM/Análise e acrescenta o subtítulo no dicionário. Co-authored-by: Cursor <cursoragent@cursor.com>
ECC Tools / Security EvidenceCommit: Security scanner evidence required (action_required) Detected 1 security-sensitive predictive risk signal(s) without scanner evidence. Mode: enforce Findings:
Touched security-sensitive paths:
Expected evidence:
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / PR Risk TaxonomyCommit: PR taxonomy review recommended (neutral) Detected 3 PR taxonomy bucket(s): Security Evidence, CI/CD Recommendation, Cost/Token Risk. Scanned 11 changed file(s). Roadmap taxonomy buckets: Security EvidenceSecurity-sensitive changes should carry explicit scanner, code-scanning, or focused regression evidence. Signals:
Paths:
CI/CD RecommendationCI, dependency, coverage, and contract signals should be routed into follow-up checks or verification work. Signals:
Paths:
Cost/Token RiskAI routing, usage, and token-budget changes should include budget or usage-limit evidence. Signals:
Paths:
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / Reference Set ReadinessCommit: Reference set readiness gaps detected (neutral) Reference evidence present for 0/7 areas (0%) across 11 changed file(s). This check is based on files changed in this PR. Repository-level readiness is still reported by
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / Hosted Promotion ReadinessCommit: Hosted promotion readiness passed (success) No hosted promotion evidence gaps detected across 11 changed file(s); 0 corpus scenarios had matching evidence. This check compares PR file changes against the evaluator/RAG promotion corpus in No evaluator corpus scenarios matched this PR. Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / PR Config AuditCommit: No changed-config issues detected (success) Scanned 3 config file(s) present at this commit across 3 changed config path(s) and found no issues in the supported security rules. Changed config files:
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / PR Harness AuditCommit: No harness issues detected (success) Scanned 3 changed config file(s) and found no harness issues. Changed config files:
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
…dioma escolhido Convergência independente com o melgarafael#744 (@biopaul), que entrou logo antes: os dois acharam que o hub de IA ficava em português mesmo com o idioma em espanhol. O conflito foi em `app/app/ai/page.tsx`, e os dois lados estavam certos sobre a causa. Ficou o do melgarafael#744 porque ele é estritamente mais forte: melgarafael#806: title="Agente de IA" locale={user.idioma} melgarafael#744: title={traduzir("Agente de IA", idioma)} locale={idioma} `idioma` é `user.idioma` — mesma fonte. A diferença é que o melgarafael#744 **também traduz** o título e o subtítulo, enquanto o melgarafael#806 os deixa cravados em português e corrige só o locale repassado ao `NavHub`. Escolher o outro lado deixaria duas strings visíveis sem tradução. O resto do melgarafael#806 entra inteiro — a entrada no dicionário e os testes dele, que cobrem a asserção pelo lado de cá. Co-authored-by: alexneverland <alexneverland@users.noreply.github.com>
…anhol trouxeram O melgarafael#744 (@biopaul) e o melgarafael#806 (@alexneverland) acharam o mesmo buraco — o hub de IA em português com o idioma em espanhol — e traduziram as mesmas chaves. Cada um acrescentou no fim do dicionário, então a resolução de conflito por apêndice ("os dois lados ficam") produziu 24 propriedades repetidas e o `tsc` reprovou com TS1117. **Este é o limite da regra do apêndice, e vale escrever:** ficar com os dois lados é certo quando eles acrescentam coisas DIFERENTES no mesmo lugar. Quando acrescentam a MESMA chave, o resultado não compila — e num arquivo de 8 mil linhas isso não se vê lendo o diff. Deduplicado mantendo, de cada par, a entrada com mais idiomas (empate: a primeira). Seis dos pares eram a mesma chave escrita com e sem aspas (`Alertas:` e `"Alertas":`), que em TS é a mesma propriedade. Medido que nada se perdeu, com o nome normalizado (sem aspas), que é a régua certa — a primeira medição comparava com aspas e acusou seis chaves "sumidas" que eram exatamente as duplicatas: chaves únicas antes: 5362 depois: 5362 sumiram: nenhuma typecheck: exit 0 nav-hub.test.tsx + ai/page.test.tsx: 9/9 Co-authored-by: biopaul <biopaul@users.noreply.github.com> Co-authored-by: alexneverland <alexneverland@users.noreply.github.com>
|
O seu trabalho está publicado na v1.24.0. Não é "mergeado": é o que uma VPS recebe quando roda A palavra que decide é O número ninguém digitou: foi calculado a partir do que cada fragmento declarou sobre o efeito em quem opera. Obrigado por isto. |
2 participants
Summary
entregarAviso(toasts da esquina / CRM / inbound) viatraduzir+idiomaAtual, no mesmo padrão deshowApiError.useT()/t().dicionario.ts.Why
Com idioma
es, vários avisos e itens de menu continuavam em português: ou o código não chamavat(), ou a chave do catálogo não existia no dicionário (degradação silenciosa para o PT).Test plan
pnpm exec vitest run tests/unit/i18n-espanhol-cobre-a-tela.test.ts(5/5)pt-BRinalterado (chave = texto PT)