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

139 lines
5.0 KiB
TypeScript

import { OnboardingComponentsContext, createInstallation } from 'scenes/onboarding/shared/OnboardingDocsContentWrapper'
import { StepDefinition } from '../steps'
export const getDotNetSteps = (ctx: OnboardingComponentsContext): StepDefinition[] => {
const { CodeBlock, Markdown, dedent } = ctx
const installStep: StepDefinition = {
title: 'Install the package',
badge: 'required',
content: (
<>
<Markdown>Install the Insights package for your .NET app:</Markdown>
<CodeBlock
blocks={[
{
language: 'bash',
file: 'ASP.NET Core',
code: dedent`
dotnet add package Insights.AspNetCore
`,
},
{
language: 'bash',
file: 'Console or worker',
code: dedent`
dotnet add package Insights
`,
},
]}
/>
</>
),
}
const configureStep: StepDefinition = {
title: 'Configure Insights',
badge: 'required',
content: (
<>
<Markdown>Register Insights and configure your project token and host:</Markdown>
<CodeBlock
blocks={[
{
language: 'csharp',
file: 'Program.cs',
code: dedent`
using Insights;
var builder = WebApplication.CreateBuilder(args);
builder.AddInsights();
`,
},
{
language: 'json',
file: 'appsettings.json',
code: dedent`
{
"Insights": {
"ProjectToken": "<ph_project_token>",
"HostUrl": "<ph_client_api_host>"
}
}
`,
},
]}
/>
</>
),
}
const captureStep: StepDefinition = {
title: 'Manually capture exceptions',
badge: 'required',
content: (
<>
<Markdown>
{dedent`
Capture handled exceptions with \`CaptureException\` so they appear in Error tracking.
`}
</Markdown>
<CodeBlock
blocks={[
{
language: 'csharp',
file: 'C#',
code: dedent`
using Insights;
void CaptureCheckoutException(IInsightsClient insights)
{
try
{
throw new InvalidOperationException("Something went wrong");
}
catch (Exception exception)
{
insights.CaptureException(
exception,
"user_distinct_id",
new Dictionary<string, object>
{
["route"] = "/checkout",
},
groups: null,
sendFeatureFlags: false
);
throw;
}
}
`,
},
]}
/>
</>
),
}
const verifyStep: StepDefinition = {
title: 'Verify error tracking',
badge: 'recommended',
checkpoint: true,
content: (
<Markdown>
{dedent`
Confirm exception events are being captured and sent to Insights. You should see events appear in the activity feed.
[Check for exceptions in Insights](https://app.hanzo.ai/activity/explore)
`}
</Markdown>
),
}
return [installStep, configureStep, captureStep, verifyStep]
}
export const DotNetInstallation = createInstallation(getDotNetSteps)