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]>
102 lines
3.3 KiB
TypeScript
102 lines
3.3 KiB
TypeScript
/**
|
|
* Test for theme mutation with DynamicColorIOS optimization.
|
|
*
|
|
* This tests that updateTheme() properly triggers re-renders on iOS
|
|
* even when using DynamicColorIOS optimization (which avoids tracking
|
|
* theme keys for performance).
|
|
*
|
|
* The fix ensures forceUpdateThemes() properly forces re-renders
|
|
* regardless of whether theme keys were tracked.
|
|
*
|
|
* NOTE: Uses launchApp({ newInstance: true }) instead of reloadReactNative() to
|
|
* avoid transient Metro module resolution errors during reload (the addTheme/
|
|
* updateTheme runtime mutations can confuse Metro's module cache on reload).
|
|
*/
|
|
|
|
import { by, device, element, expect, waitFor } from 'detox'
|
|
import { remountDirectUseCase } from './utils/navigation'
|
|
import { safeLaunchApp } from './utils/detox'
|
|
|
|
const cycleThemeColor = () => {
|
|
return device.openURL({ url: 'hanzogui-kitchen-sink://theme-mutation-next' })
|
|
}
|
|
|
|
describe('ThemeMutation', () => {
|
|
beforeAll(async () => {
|
|
await safeLaunchApp({
|
|
newInstance: true,
|
|
launchArgs: { directUseCase: 'ThemeMutation' },
|
|
})
|
|
await waitFor(element(by.id('theme-mutation-button')))
|
|
.toExist()
|
|
.withTimeout(180000)
|
|
})
|
|
|
|
beforeEach(async () => {
|
|
await remountDirectUseCase('theme-mutation-button', {
|
|
skipEnableSync: true,
|
|
})
|
|
})
|
|
|
|
it('should navigate to ThemeMutation test case', async () => {
|
|
await waitFor(element(by.id('theme-mutation-button')))
|
|
.toBeVisible()
|
|
.withTimeout(5000)
|
|
})
|
|
|
|
it('should show initial red color', async () => {
|
|
// verify the initial color text shows red
|
|
await waitFor(element(by.id('theme-mutation-color-text')))
|
|
.toHaveText('Expected color: red')
|
|
.withTimeout(5000)
|
|
// verify the square is visible
|
|
await waitFor(element(by.id('theme-mutation-square')))
|
|
.toBeVisible()
|
|
.withTimeout(5000)
|
|
})
|
|
|
|
it('should update theme color when button is pressed', async () => {
|
|
// initial state should be red
|
|
await waitFor(element(by.id('theme-mutation-color-text')))
|
|
.toHaveText('Expected color: red')
|
|
.withTimeout(5000)
|
|
|
|
await cycleThemeColor()
|
|
|
|
// wait for the color to update to blue
|
|
await waitFor(element(by.id('theme-mutation-color-text')))
|
|
.toHaveText('Expected color: blue')
|
|
.withTimeout(5000)
|
|
|
|
// verify the square is still visible (component re-rendered)
|
|
await waitFor(element(by.id('theme-mutation-square')))
|
|
.toBeVisible()
|
|
.withTimeout(5000)
|
|
})
|
|
|
|
it('should cycle through multiple theme colors', async () => {
|
|
const colors = ['red', 'blue', 'green', 'purple', 'orange']
|
|
|
|
for (let i = 0; i < colors.length; i++) {
|
|
const expectedColor = colors[i]
|
|
await waitFor(element(by.id('theme-mutation-color-text')))
|
|
.toHaveText(`Expected color: ${expectedColor}`)
|
|
.withTimeout(5000)
|
|
|
|
// tap to cycle to next color (except on last iteration)
|
|
if (i < colors.length - 1) {
|
|
await cycleThemeColor()
|
|
await waitFor(element(by.id('theme-mutation-color-text')))
|
|
.toHaveText(`Expected color: ${colors[i + 1]}`)
|
|
.withTimeout(5000)
|
|
}
|
|
}
|
|
|
|
// verify it cycles back to red after orange
|
|
await cycleThemeColor()
|
|
await waitFor(element(by.id('theme-mutation-color-text')))
|
|
.toHaveText('Expected color: red')
|
|
.withTimeout(5000)
|
|
})
|
|
})
|