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

112 lines
4.5 KiB
TypeScript

import { OnboardingComponentsContext, createInstallation } from 'scenes/onboarding/shared/OnboardingDocsContentWrapper'
import { getFlutterSteps } from '../product-analytics/flutter'
import { StepDefinition } from '../steps'
function getSurveysFlutterSteps(ctx: OnboardingComponentsContext): StepDefinition[] {
const { CodeBlock, Markdown, dedent, snippets } = ctx
const SurveysFinalSteps = snippets?.SurveysFinalSteps
const installationSteps = getFlutterSteps(ctx)
const surveysSteps: StepDefinition[] = [
{
title: 'Install InsightsObserver',
badge: 'required',
content: (
<>
<Markdown>
For surveys to be shown, you need to add the InsightsObserver to your app. The observer allows
Insights to determine the appropriate context for displaying surveys.
</Markdown>
<CodeBlock
blocks={[
{
language: 'dart',
file: 'main.dart',
code: dedent`
import 'package:flutter/material.dart';
import 'package:insights_flutter/insights_flutter.dart';
class MyApp extends StatefulWidget {
const MyApp({super.key});
@override
State<MyApp> createState() => _MyAppState();
}
class _MyAppState extends State<MyApp> {
@override
void initState() {
super.initState();
}
@override
Widget build(BuildContext context) {
return InsightsWidget(
child: MaterialApp(
navigatorObservers: [InsightsObserver()],
title: 'My App',
home: const HomeScreen(),
),
);
}
}
`,
},
]}
/>
<Markdown>
{dedent`
If you're using go_router, check [this page](https://hanzo.ai/docs/surveys/installation/flutter) to learn how to set up the InsightsObserver.
`}
</Markdown>
</>
),
},
{
title: 'Configuration',
badge: 'optional',
content: (
<>
<Markdown>
**Important:** For Flutter Web, surveys are powered by the JavaScript Web SDK, so any
Flutter-specific survey configuration will be ignored. Please refer to the Web installation
guide for proper setup.
</Markdown>
<Markdown>
Surveys are enabled by default. If you want to disable surveys, you can do so when setting up
your SDK instance:
</Markdown>
<CodeBlock
blocks={[
{
language: 'dart',
file: 'main.dart',
code: dedent`
final config = InsightsConfig('<ph_project_token>');
config.surveys = false; // Disable surveys
`,
},
]}
/>
</>
),
},
]
return [
...installationSteps,
...surveysSteps,
{
title: 'Next steps',
badge: 'recommended',
content: <>{SurveysFinalSteps && <SurveysFinalSteps />}</>,
},
]
}
export const SurveysFlutterInstallation = createInstallation(getSurveysFlutterSteps)