mirror of
https://github.com/hanzoai/gui.git
synced 2026-10-25 02:31:41 +00:00
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]>
43 lines
1.5 KiB
TypeScript
43 lines
1.5 KiB
TypeScript
import { expect, test } from '@playwright/test'
|
|
import { setupPage } from './test-utils'
|
|
|
|
/**
|
|
* Test for issue #3565
|
|
* Verifies that Dialog works when controlled with open={true}
|
|
*
|
|
* In JSDOM (Jest), this fails with "node.show is not a function"
|
|
* because JSDOM doesn't implement HTMLDialogElement.show()
|
|
*
|
|
* This test ensures the dialog renders correctly in a real browser.
|
|
*/
|
|
test.describe('Dialog Open Controlled', () => {
|
|
test.beforeEach(async ({ page }) => {
|
|
await setupPage(page, { name: 'DialogOpenControlled', type: 'useCase' })
|
|
})
|
|
|
|
test('dialog renders when controlled with open={true}', async ({ page }) => {
|
|
await page.waitForLoadState('networkidle')
|
|
|
|
// The dialog should be visible immediately since open={true}
|
|
const dialogContent = page.getByTestId('dialog-content')
|
|
await expect(dialogContent).toBeVisible({ timeout: 5000 })
|
|
await expect(dialogContent).toHaveText('Hiya!')
|
|
})
|
|
|
|
test('dialog can be closed via close button', async ({ page }) => {
|
|
await page.waitForLoadState('networkidle')
|
|
|
|
// Dialog should be visible
|
|
const dialogContent = page.getByTestId('dialog-content')
|
|
await expect(dialogContent).toBeVisible({ timeout: 5000 })
|
|
|
|
// Click close button
|
|
const closeButton = page.getByTestId('dialog-close')
|
|
await closeButton.click()
|
|
|
|
// Dialog should still be visible because it's controlled with open={true}
|
|
// (no state management in the component - it's always open)
|
|
await expect(dialogContent).toBeVisible()
|
|
})
|
|
})
|