Files
zeekay 1b367e2b62 chore: rebase the tree onto upstream master
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.
2026-08-01 15:44:40 -07:00

128 lines
6.3 KiB
TypeScript

import { OnboardingComponentsContext, createInstallation } from 'scenes/onboarding/shared/OnboardingDocsContentWrapper'
import { getReactSteps as getReactStepsPA } from '../product-analytics/react'
import { StepDefinition } from '../steps'
export const getReactSteps = (ctx: OnboardingComponentsContext): StepDefinition[] => {
const { CodeBlock, Markdown, dedent, Tab, snippets } = ctx
const BooleanFlag = snippets?.BooleanFlagSnippet
const MultivariateFlag = snippets?.MultivariateFlagSnippet
const FlagPayload = snippets?.FlagPayloadSnippet
// Get installation steps from product-analytics
const installationSteps = getReactStepsPA(ctx)
// Add flag-specific steps
const flagSteps: StepDefinition[] = [
{
title: 'Use feature flags',
badge: 'required',
content: (
<Tab.Group tabs={['Using hooks', 'Using InsightsFeature component']}>
<Tab.List>
<Tab>Using hooks</Tab>
<Tab>Using InsightsFeature component</Tab>
</Tab.List>
<Tab.Panels>
<Tab.Panel>
<Markdown>
{dedent`
Insights provides several hooks to make it easy to use feature flags in your React app. Use \`useFeatureFlagEnabled\` for boolean flags:
`}
</Markdown>
{BooleanFlag && <BooleanFlag language="react" />}
<Markdown>
{dedent`
### Multivariate flags
For multivariate flags, use \`useFeatureFlagVariantKey\`:
`}
</Markdown>
{MultivariateFlag && <MultivariateFlag language="react" />}
<Markdown>
{dedent`
### Flag payloads
The \`useFeatureFlagPayload\` hook does *not* send a \`$feature_flag_called\` event, which is required for experiments. Always use it with \`useFeatureFlagEnabled\` or \`useFeatureFlagVariantKey\`:
`}
</Markdown>
{FlagPayload && <FlagPayload language="react" />}
</Tab.Panel>
<Tab.Panel>
<Markdown>
{dedent`
The \`InsightsFeature\` component simplifies code by handling feature flag related logic:
`}
</Markdown>
<CodeBlock
blocks={[
{
language: 'jsx',
file: 'App.tsx',
code: dedent`
import { InsightsFeature } from '@hanzo/react'
function App() {
return (
<InsightsFeature flag='show-welcome-message' match={true}>
<div>
<h1>Hello</h1>
<p>Thanks for trying out our feature flags.</p>
</div>
</InsightsFeature>
)
}
`,
},
]}
/>
<Markdown>
{dedent`
The \`match\` prop can be either \`true\`, or the variant key, to match on a specific variant. If you also want to show a default message, you can pass these in the \`fallback\` prop.
If your flag has a payload, you can pass a function to children whose first argument is the payload:
`}
</Markdown>
<CodeBlock
blocks={[
{
language: 'jsx',
file: 'App.tsx',
code: dedent`
<InsightsFeature flag='show-welcome-message' match={true}>
{(payload) => {
return (
<div>
<h1>{payload.welcomeMessage}</h1>
<p>Thanks for trying out our feature flags.</p>
</div>
)
}}
</InsightsFeature>
`,
},
]}
/>
</Tab.Panel>
</Tab.Panels>
</Tab.Group>
),
},
{
title: 'Running experiments',
badge: 'optional',
content: (
<Markdown>
{dedent`
Experiments run on top of our feature flags. Once you've implemented the flag in your code, you run an experiment by creating a new experiment in the Insights dashboard.
`}
</Markdown>
),
},
]
return [...installationSteps, ...flagSteps]
}
export const ReactInstallation = createInstallation(getReactSteps)