mirror of
https://github.com/hanzoai/gui.git
synced 2026-10-25 02:31:41 +00:00
zeekayandHanzo Dev
69c6e860d7
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]>
46 lines
1.8 KiB
TypeScript
46 lines
1.8 KiB
TypeScript
import { expect, test } from '@playwright/test'
|
|
import { setupPage } from './test-utils'
|
|
import { getStyles } from './utils'
|
|
import { TEST_IDS } from '../src/constants/test-ids'
|
|
|
|
/**
|
|
* Tests for GitHub issue #3620: Theme switching broken after v1.132.15
|
|
*
|
|
* Color tokens should act as fallbacks - if a theme defines a value for the same key,
|
|
* the theme value should take precedence over the color token.
|
|
*
|
|
* The bug was that Object.assign(theme, colorTokens) was overwriting theme values
|
|
* with color token values instead of the other way around.
|
|
*/
|
|
|
|
test.beforeEach(async ({ page }) => {
|
|
await setupPage(page, { name: 'ColorTokenFallback', type: 'useCase' })
|
|
})
|
|
|
|
test('theme value takes precedence over color token', async ({ page }) => {
|
|
// The light_ColorTokenTest theme defines customRed as #00ff00 (green)
|
|
// The color token customRed is #ff0000 (red)
|
|
// The theme value should win, so the background should be green
|
|
const square = page.locator(`#${TEST_IDS.colorTokenFallbackThemeValue}`)
|
|
await expect(square).toBeVisible()
|
|
|
|
const styles = await getStyles(square)
|
|
// rgb(0, 255, 0) is #00ff00 (green) - the theme value
|
|
// rgb(255, 0, 0) would be #ff0000 (red) - the color token value (wrong)
|
|
expect(styles.backgroundColor).toBe('rgb(0, 255, 0)')
|
|
})
|
|
|
|
test('color token is used as fallback when theme does not define it', async ({
|
|
page,
|
|
}) => {
|
|
// The light_ColorTokenTest theme does NOT define customBlue
|
|
// The color token customBlue is #0000ff (blue)
|
|
// The color token should be used as a fallback
|
|
const square = page.locator(`#${TEST_IDS.colorTokenFallbackTokenValue}`)
|
|
await expect(square).toBeVisible()
|
|
|
|
const styles = await getStyles(square)
|
|
// rgb(0, 0, 255) is #0000ff (blue) - the color token fallback
|
|
expect(styles.backgroundColor).toBe('rgb(0, 0, 255)')
|
|
})
|