mirror of
https://github.com/hanzoai/insights.git
synced 2026-10-30 16:15:31 +00:00
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.
99 lines
4.2 KiB
TypeScript
99 lines
4.2 KiB
TypeScript
import { OnboardingComponentsContext, createInstallation } from 'scenes/onboarding/shared/OnboardingDocsContentWrapper'
|
|
|
|
import { getReactNativeSteps as getReactNativeStepsPA } from '../product-analytics/react-native'
|
|
import { StepDefinition } from '../steps'
|
|
|
|
export const getReactNativeSteps = (ctx: OnboardingComponentsContext): StepDefinition[] => {
|
|
const { CodeBlock, Markdown, dedent } = ctx
|
|
|
|
// Get installation steps from product-analytics
|
|
const installationSteps = getReactNativeStepsPA(ctx)
|
|
|
|
// Add flag-specific steps
|
|
const flagSteps: StepDefinition[] = [
|
|
{
|
|
title: 'Use feature flags',
|
|
badge: 'required',
|
|
content: (
|
|
<>
|
|
<Markdown>
|
|
{dedent`
|
|
Insights provides hooks to make it easy to use feature flags in your React Native app. Use \`useFeatureFlagEnabled\` for boolean flags:
|
|
`}
|
|
</Markdown>
|
|
<CodeBlock
|
|
blocks={[
|
|
{
|
|
language: 'tsx',
|
|
file: 'Component.tsx',
|
|
code: dedent`
|
|
import { useInsights } from 'insights-react-native'
|
|
|
|
function MyComponent() {
|
|
const insights = useInsights()
|
|
const isMyFlagEnabled = insights.isFeatureEnabled('flag-key')
|
|
|
|
if (isMyFlagEnabled) {
|
|
// Do something differently for this user
|
|
// Optional: fetch the payload
|
|
const matchedFlagPayload = insights.getFeatureFlagResult('flag-key')?.payload
|
|
}
|
|
|
|
return <View>...</View>
|
|
}
|
|
`,
|
|
},
|
|
]}
|
|
/>
|
|
<Markdown>
|
|
{dedent`
|
|
### Multivariate flags
|
|
|
|
For multivariate flags, use \`getFeatureFlag\`:
|
|
`}
|
|
</Markdown>
|
|
<CodeBlock
|
|
blocks={[
|
|
{
|
|
language: 'tsx',
|
|
file: 'Component.tsx',
|
|
code: dedent`
|
|
import { useInsights } from 'insights-react-native'
|
|
|
|
function MyComponent() {
|
|
const insights = useInsights()
|
|
const enabledVariant = insights.getFeatureFlag('flag-key')
|
|
|
|
if (enabledVariant === 'variant-key') { // replace 'variant-key' with the key of your variant
|
|
// Do something differently for this user
|
|
// Optional: fetch the payload
|
|
const matchedFlagPayload = insights.getFeatureFlagResult('flag-key')?.payload
|
|
}
|
|
|
|
return <View>...</View>
|
|
}
|
|
`,
|
|
},
|
|
]}
|
|
/>
|
|
</>
|
|
),
|
|
},
|
|
{
|
|
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 ReactNativeInstallation = createInstallation(getReactNativeSteps)
|