mirror of
https://github.com/hanzoai/insights.git
synced 2026-10-30 16:15:31 +00:00
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.
46 lines
1.8 KiB
TypeScript
46 lines
1.8 KiB
TypeScript
import { OnboardingComponentsContext, createInstallation } from 'scenes/onboarding/shared/OnboardingDocsContentWrapper'
|
|
|
|
import { getFlutterSteps as getFlutterStepsPA } from '../product-analytics/flutter'
|
|
import { StepDefinition } from '../steps'
|
|
|
|
export const getFlutterSteps = (ctx: OnboardingComponentsContext): StepDefinition[] => {
|
|
const { Markdown, dedent, snippets } = ctx
|
|
const ExperimentImplementation = snippets?.ExperimentImplementationSnippet
|
|
|
|
// Get installation steps from product-analytics only
|
|
const installationSteps = getFlutterStepsPA(ctx).filter((step: StepDefinition) => step.title !== 'Send events')
|
|
|
|
// Add experiments-specific steps
|
|
const experimentSteps: StepDefinition[] = [
|
|
{
|
|
title: 'Implement your experiment',
|
|
badge: 'required',
|
|
content: (
|
|
<>
|
|
<Markdown>
|
|
{dedent`
|
|
Experiments run on top of our feature flags. You can define which version of your code runs based on the return value of the feature flag:
|
|
`}
|
|
</Markdown>
|
|
{ExperimentImplementation && <ExperimentImplementation language="flutter" />}
|
|
</>
|
|
),
|
|
},
|
|
{
|
|
title: 'Run your experiment',
|
|
badge: 'required',
|
|
content: (
|
|
<Markdown>
|
|
{dedent`
|
|
Once you've implemented the feature flag in your code, you'll enable it for a target audience by creating a new experiment in the Insights dashboard.
|
|
`}
|
|
</Markdown>
|
|
),
|
|
},
|
|
]
|
|
|
|
return [...installationSteps, ...experimentSteps]
|
|
}
|
|
|
|
export const FlutterInstallation = createInstallation(getFlutterSteps)
|