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]>
1.7 KiB
1.7 KiB
@hanzogui/use-store
Simplish reactive classes in react. It doesn't do granular deep object reaction, just the top level set.
import {
createUseStore,
createStoreInstance,
useStore,
useGlobalStore,
} from '@hanzogui/use-store'
class X {
y = 0
add() {
this.y += 1
}
}
// Can use it a few ways, all these will access *the same* store:
const useX = createUseStore(X)
const x = createStoreInstance(X)
// all of these will be reactive, so only props you use cause re-renders
export function ReactComponent() {
const x0 = useStore(X)
const x1 = useX()
const x2 = useGlobalStore(x)
return (
<>
<div>{x0.y}</div>
<button action={x0.add}>add</button>
</>
)
}
// if you want a different instance or namespace, pass props, these will also all access the same store:
export function ReactComponentAlt() {
const x0 = useStore(X, { id: 100 })
const x1 = useX({ id: 100 })
const x2 = useGlobalStore(x, { id: 100 })
return <div>{x0.y}</div>
}
// finally, you can make selectors with
export function ReactComponentAlt() {
const xplusten0 = useStoreSelector(X, { id: 100 }, (x) => x.y + 10)
const xplusten1 = useGlobalStoreSelector(X, { id: 100 }, (x) => x.y + 10)
return <div>{xplusten}</div>
}
TODO
- usePortal
Better selectors/reactions:
- useSelector
- reaction
Basically make them not tied to one store:
const isValid = useStoreSelector(() => {
return mapStore.isActive && homeStore.isActive
})
Same with reaction:
useEffect(() => {
return reaction(
() => {
return homeStore.isActive && mapStore.isActive
},
(isValid) => {
// ...
}
)
}, [])
Note it does shallow compare.