zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
1.6 KiB
Storybook
Adding new Tailwind classes
Tailwind is compiled by @tailwindcss/postcss on the initial build. Webpack's
HMR does not re-run PostCSS when story content changes, so a newly used
Tailwind utility (e.g. bg-[rebeccapurple]) won't appear until you restart
Storybook. Classes already present in the codebase hot-reload fine.
Storybook visual regression tests
In CI we use playwright to load our storybooks scenes and take snapshots of them
If they have changed we commit those snapshots back to the PR
This lets you check if you have broken the UI unexpectedly or changed it in the way you expected
You can check test-runner.ts to see how this is done
Uses "@storybook/test-runner" see: https://storybook.js.org/docs/writing-tests/test-runner
to run locally
before you do this... 🤷
in one terminal
insightscli storybook
in another
pnpm exec playwright install
insightscli storybook:test
Viewport width variants
You can snapshot a story at multiple viewport widths
by setting viewportWidths in testOptions.
This produces one snapshot per width instead of the default single snapshot.
Available widths: narrow (568px), medium (960px), wide (1300px), superwide (1920px).
export const MyStoryViewports: Story = createInsightStory(fixture, 'edit')
MyStoryViewports.parameters = {
testOptions: {
viewportWidths: ['medium', 'wide', 'superwide'],
},
}
Each width generates a separate snapshot file suffixed with the width name,
e.g. my-story-viewports--medium--light.png.
See frontend/src/scenes/insights/stories/TrendsLine.stories.tsx for a working example.