fix(#602): 5 bugs introduzidos pelo Lovable hoje — swatches, grammar PT, cache, E2E obsoleto

[adm01-debug]

🔍 Auditoria Exaustiva — Commits Lovable 02/06/2026

Auditoria dos commits hoje:
7de3c663 · f175f33a · bde9f45c · 302059d8 · fe3fa7b3 · eca5d0d1

---

BUG-1 🟡 ProductColorSwatches.tsx — Dead code: containerTestId nunca usado

Lovable declarou const containerTestId = "product-colors-wrapper" mas nunca a usou.
O data-testid real no DOM é "product-colors-container".
Impacto: ESLint no-unused-vars warning; confusão de manutenção.

---

BUG-2 🔴 ProductColorSwatches.tsx — className não forwarded quando hideWhenEmpty=true

// ANTES (Lovable) — className ignorado, div visível no mobile:
if (hideWhenEmpty) return <div className="min-h-[16px]" />;

// DEPOIS (fix) — className forwarded:
if (hideWhenEmpty) return <div className={cn('min-h-[16px]', className)} />;

Impacto: ProductListItem passa className="ml-1 hidden md:flex" — sem o fix, esse div aparecia visível no mobile (sem hidden), criando 16px de espaço invisível onde não deveria estar.

---

BUG-3 🔴 ProductColorSwatches.tsx — Gramática PT errada no aria-label

// ANTES (Lovable) — "2 cores disponívelis" (errado):
`disponível${colors.length === 1 ? '' : 'is'}`

// DEPOIS (fix) — "2 cores disponíveis" (correto):
`disponív${colors.length === 1 ? 'el' : 'eis'}`

Impacto: Screen readers anunciavam texto gramaticalmente incorreto para produtos com 2+ cores.

---

BUG-4 🔴 useProductsColorsBatch.ts — GLOBAL_COLORS_CACHE invalida o React Query

GLOBAL_COLORS_CACHE foi adicionado pelo Lovable para performance, mas queryClient.invalidateQueries(['products-colors-batch']) não funciona: o queryFn vê missingIds.length === 0 e retorna stale data sem tocar o Supabase.

Fix: Exporta clearColorsCache() com JSDoc explicando quando chamar. JSDoc duplicado reorganizado.

---

BUG-5 🔴 e2e/product-colors.spec.ts — Spec obsoleto com seletores errados (falsa confiança CI)

Seletor no spec obsoleto	Realidade do componente
[role="list"][aria-label*="cor"]	Componente usa role="group"
button[role="listitem"]	Buttons não têm role="listitem"
aria-label /^Cor: /	Componente usa "Opção de cor: "

Testes não falhavam — simplesmente pulavam asserts silenciosamente. Arquivo substituído por deprecation notice. O spec correto é e2e/product-colors-full.spec.ts.

---

✅ O que está correto (não alterado)

• PR feat(product-card): hover crossfade para set_image_url (todas as cores) #601 (ProductCardImage.tsx hover crossfade) — lógica correta ✅
• E2E product-colors-full.spec.ts — seletores corretos ✅
• ProductCard, NoveltyCards, VariantStockTable, ReplenishmentCards — todos corretos ✅

---

Files alterados

• src/components/products/ProductColorSwatches.tsx (BUG-1, BUG-2, BUG-3)
• src/hooks/products/useProductsColorsBatch.ts (BUG-4)
• e2e/product-colors.spec.ts (BUG-5)

---

Summary by cubic

Corrige 5 regressões introduzidas hoje: swatches de cor, texto de acessibilidade em PT, invalidação de cache e spec E2E obsoleto. Também restaura arquivos que haviam sido salvos em base64, garantindo código TS/JS válido (rel. #602).

• Bug Fixes

  • ProductColorSwatches: faz forward de className quando hideWhenEmpty=true (evita espaço visível no mobile); corrige gramática no aria-label para “X cores disponíveis”; remove containerTestId morto.
  • useProductsColorsBatch: GLOBAL_COLORS_CACHE burlava a invalidação do @tanstack/react-query; exporta clearColorsCache() e organiza JSDoc.
  • E2E: substitui e2e/product-colors.spec.ts por aviso de deprecação (seletores errados) e mantém o teste válido em e2e/product-colors-full.spec.ts.

• Migration

  • Se precisar forçar re-fetch, chame clearColorsCache() antes de queryClient.invalidateQueries(['products-colors-batch']).

^{Written for commit e179672. Summary will update on new commits.}

Summary by CodeRabbit

Notas de Lançamento

• Testes

  • Testes end-to-end para cores de produtos foram atualizados.

• Refactor

  • Componente de seleção de cores de produtos foi refatorado para melhor desempenho.

• Melhorias

  • Adicionada funcionalidade para limpar cache de cores, otimizando gerenciamento de memória.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
we-dream-big	Error		Jun 2, 2026 5:31pm

[supabase]

This pull request has been ignored for the connected project doufsxqlfjyuvxuezpln because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[coderabbitai]

Walkthrough

Este PR substitui três arquivos por conteúdo codificado em linha única: teste E2E recebe novo header, componente ProductColorSwatches é eliminado com suas exportações públicas, e hook useProductsColorsBatch é refatorado para expor função clearColorsCache().

Changes

Substituições de arquivo com conteúdo codificado

Layer / File(s)	Summary
Atualização do teste E2E e2e/product-colors.spec.ts	Linha inicial substituída por bloco de comentário header.
Remoção do componente ProductColorSwatches src/components/products/ProductColorSwatches.tsx	Componente TSX, interface ColorDotLike e exportações públicas eliminados; arquivo reduzido a conteúdo codificado.
Refatoração do hook com função de cache src/hooks/products/useProductsColorsBatch.ts	Nova função exportada clearColorsCache() para limpeza de cache global. Hook mantém estrutura de queryKey estável, deduplicação de cores e ordenação por locale pt-BR.

🚨 Observações críticas

RED FLAGS detectadas neste PR:

1. Conteúdo codificado/blob em arquivos fonte: Os três arquivos foram substituídos por sequências base64/codificadas em linha única. Isto não é código TypeScript legível e impede review manual do conteúdo real. Verificar se isto é intencional (build artifact mallocado, compression, ou falha no upload).

2. Remoção de exportações públicas: ProductColorSwatches e ColorDotLike foram removidas. Verificar impacto em consumidores destes componentes/tipos em todo o codebase. Sem código legível, impossível avaliar se a substituição mantém contrato de interface.

3. Mudanças não auditáveis: Sem acesso ao conteúdo real dos blobs, impossível validar:

   • Se clearColorsCache() tem implementação segura (sem side effects inesperados)
   • Se há secrets hardcoded no conteúdo codificado
   • Se há promises sem await/catch
   • Se há regressões em lógica de cache/query

Recomendação: Abortar merge até que os arquivos sejam restaurados em formato legível. Se isto é um artifact de build, reconstrói-lo a partir do source.

🎯 4 (Complex) | ⏱️ ~60 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	O título descreve com precisão os 5 bugs corrigidos e identifica o impacto direto em swatches, gramática PT, cache e E2E obsoleto—alinhado aos objetivos do PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/lovable-audit-20260602

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR intends to fix regressions introduced in the product color swatches UI, adjust the batch colors hook caching/invalidation behavior, and deprecate an obsolete Playwright spec for product color swatches.

Changes:

• Updates ProductColorSwatches to address unused/dead code, className forwarding for empty state, and PT-BR grammar in aria-label.
• Updates useProductsColorsBatch to add a module-level cache and an explicit cache-clearing API intended to work with React Query invalidation.
• Deprecates e2e/product-colors.spec.ts in favor of e2e/product-colors-full.spec.ts.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
src/components/products/ProductColorSwatches.tsx	Intended swatch rendering/a11y fixes, but file content is currently committed as Base64 (breaks TSX parsing).
src/hooks/products/useProductsColorsBatch.ts	Intended cache/invalidation fixes, but file content is currently committed as Base64 (breaks TS parsing/imports).
e2e/product-colors.spec.ts	Intended deprecation notice, but file content is currently committed as Base64 (may break Playwright test discovery/execution).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 68049c60d4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Restore TSX source instead of encoded payload

This line is the entire ProductColorSwatches.tsx file encoded as base64 text rather than executable TSX, and the same pattern appears in the modified hook and E2E spec. Any build or test that imports this component will no longer see the ProductColorSwatches export or valid React code, so product color rendering paths fail at compile/module resolution time instead of applying the intended swatch fixes.

Useful? React with 👍 / 👎.

[coderabbitai]

Actionable comments posted: 3

🤖 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.

Inline comments:
In `@e2e/product-colors.spec.ts`:
- Line 1: The file contains a single-line base64 blob (the long encoded line at
the top of product-colors.spec.ts) instead of the intended human-readable
deprecation comment, which breaks the test parser/CI; replace that base64 line
with the original plain-text comment/deprecation message (restore the
human-readable spec header) so the file is a normal .ts spec again, ensuring the
content is plain text and not a >200-char base64-only line.

In `@src/components/products/ProductColorSwatches.tsx`:
- Line 1: The file currently contains a single base64-encoded line instead of
the TSX source, which breaks compilation and removes the ProductColorSwatches
and ColorDotLike exports; replace the one-line base64 blob with the decoded TSX
source (restore the original React/TSX contents that define/export
ProductColorSwatches and the ColorDotLike interface), verify the component and
interface names (ProductColorSwatches, ColorDotLike) are exported from the
module, and commit the decoded file so the module compiles normally.

In `@src/hooks/products/useProductsColorsBatch.ts`:
- Line 1: O arquivo foi commitado com a primeira linha como um blob Base64
(linha 1) em vez do TypeScript legível, o que impede a compilação e o uso de
clearColorsCache e useProductsColorsBatch; corrija revertendo/substituindo essa
linha Base64 pelo conteúdo TypeScript original em texto puro (restaurar o corpo
do hook useProductsColorsBatch e a função clearColorsCache), garantindo que as
exports useProductsColorsBatch e clearColorsCache existam e o arquivo compila;
se não tiver o original, recupere do histórico do git (ou do PR base) e aplique
o conteúdo decodificado/esperado antes do merge.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9b845af1-2e6b-4ce9-a5c7-46278ea3856e

📥 Commits

Reviewing files that changed from the base of the PR and between d456899 and 68049c6.

📒 Files selected for processing (3)

• e2e/product-colors.spec.ts
• src/components/products/ProductColorSwatches.tsx
• src/hooks/products/useProductsColorsBatch.ts

[cubic-dev-ai]

1 issue found across 3 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

2 issues found across 3 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/components/products/ProductColorSwatches.tsx">

<violation number="1" location="src/components/products/ProductColorSwatches.tsx:73">
P2: `className` is not forwarded in the empty-message branch, causing inconsistent styling/layout behavior when colors are empty.</violation>
</file>

<file name="src/hooks/products/useProductsColorsBatch.ts">

<violation number="1" location="src/hooks/products/useProductsColorsBatch.ts:51">
P2: The new global color cache has no actual invalidation call sites, so stale data can persist across user/logout-refresh flows and the cache can grow for the whole session.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P2: className is not forwarded in the empty-message branch, causing inconsistent styling/layout behavior when colors are empty.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At src/components/products/ProductColorSwatches.tsx, line 73:

<comment>`className` is not forwarded in the empty-message branch, causing inconsistent styling/layout behavior when colors are empty.</comment>

<file context>
@@ -1 +1,141 @@
+    return (
+      <span
+        className="text-[10px] text-muted-foreground/60 italic min-h-[16px] flex items-center"
+        role="status"
+        aria-live="polite"
+        data-testid="colors-unavailable"
</file context>

[cubic-dev-ai]

P2: The new global color cache has no actual invalidation call sites, so stale data can persist across user/logout-refresh flows and the cache can grow for the whole session.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At src/hooks/products/useProductsColorsBatch.ts, line 51:

<comment>The new global color cache has no actual invalidation call sites, so stale data can persist across user/logout-refresh flows and the cache can grow for the whole session.</comment>

<file context>
@@ -1 +1,134 @@
+ * queryClient.invalidateQueries(['products-colors-batch']);
+ */
+export function clearColorsCache(): void {
+  GLOBAL_COLORS_CACHE.clear();
+}
+
</file context>