Files
gui/apps/kitchen-sink/tests/StyledContextTokens.test.tsx
zeekayandHanzo Dev 69c6e860d7 transplant onto tamagui v2.6.0, brand as a re-runnable transform
This repo could never sync. There was NO merge-base with tamagui — 372 commits
here against 15,791 there, unrelated histories — because it began as a
copy-paste rebrand with a flattened layout. Every "sync" since was a hand
re-application that drifted, which is why the tree sat on 7.3.1 while upstream
shipped fixes we then rediscovered by hand.

This commit's PARENT IS TAMAGUI. A future sync is `git merge tama/main` then
`node scripts/rebrand.mjs` — a real merge, because the history is now shared.

174 packages: 166 upstream, our 8 restored (chrome, shell, telemetry, recipes,
get, font-geist-{sans,mono}, @hanzo/booker), bento-get gained. 170/170 build.

Our patches to files UPSTREAM ALSO OWNS are carried, which the package-level
delta missed and which was where the value actually was:
  - useMedia's server snapshot (`initState ?? getMedia()`). Upstream still
    returns undefined there, so every Tamagui Dialog kills a prerender — the
    exact crash hanzo.app spent a day on.
  - data-slot on web host nodes, absent upstream entirely.
Both applied ONTO upstream's newer files (it rewrote useMedia +150/-63 and
createComponent +160/-55), marked `PATCH (ours, carried across the transplant)`.

Seven traps are encoded in scripts/rebrand.mjs, each found by a gate:
skip itself and lockfiles; special-case the double-branded names in BOTH scoped
and bare form; map path strings, not just paths; drop a level for the flattened
group; check disk rather than a stale index.

Rust build artifacts are NOT committed. An earlier draft of this commit swept
apps/desktop/src-tauri/target/debug in via `git add -A` — 3,859 files including
a 272MB .a, over GitHub's 100MB cap, so the push could never have landed. They
are gitignored now.

Co-Authored-By: Hanzo Dev <[email protected]>
2026-07-30 18:25:06 -07:00

57 lines
2.1 KiB
TypeScript

import { expect, test } from '@playwright/test'
import { setupPage } from './test-utils'
/**
* Tests for styled context token preservation (issues #3670, #3676)
*
* When a parent component sets a context value via a variant (like gap: '$8'),
* child components should receive the original token string ('$8') in their
* functional variants, NOT the resolved CSS variable ('var(--t-space-8)').
*
* This is important because functional variants need the token string to
* look up values in the tokens object.
*/
test.beforeEach(async ({ page }) => {
await setupPage(page, { name: 'StyledContextTokens', type: 'useCase' })
})
test('variant should pass token string to context, not CSS variable - small spacing', async ({
page,
}) => {
// The debug display shows what gap value the child received via context
const gapValue = await page.locator('#debug-small-gap-value').textContent()
// Should be '$2' (the token string), not 'var(--t-space-2)' (the CSS variable)
expect(gapValue).toBe('$2')
})
test('variant should pass token string to context, not CSS variable - large spacing', async ({
page,
}) => {
const gapValue = await page.locator('#debug-large-gap-value').textContent()
// Should be '$8' (the token string), not 'var(--t-space-8)' (the CSS variable)
expect(gapValue).toBe('$8')
})
test('default context value should be preserved as token string', async ({ page }) => {
const gapValue = await page.locator('#debug-default-gap-value').textContent()
// Default context value should also be a token string
expect(gapValue).toBe('$4')
})
test('debug display should show green background when token is preserved', async ({
page,
}) => {
// The debug display has green background if gap is a token string, red if CSS variable
const debugSmall = page.locator('#debug-small')
const bgColor = await debugSmall.evaluate((el) => getComputedStyle(el).backgroundColor)
// Green-ish color indicates token was preserved (using $green5 theme token)
// This is a sanity check that our isToken logic in the component is working
expect(bgColor).not.toBe('rgb(254, 202, 202)') // not red ($red5)
})