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

178 lines
8.4 KiB
TypeScript

import { OnboardingComponentsContext, createInstallation } from 'scenes/onboarding/shared/OnboardingDocsContentWrapper'
import { getAngularSteps as getAngularStepsPA } from '../product-analytics/angular'
import { StepDefinition } from '../steps'
export const getAngularSteps = (ctx: OnboardingComponentsContext): StepDefinition[] => {
const { CodeBlock, Markdown, dedent } = ctx
const installSteps = getAngularStepsPA(ctx)
const exceptionAutocaptureStep: StepDefinition = {
title: 'Setting up exception autocapture',
badge: 'recommended',
content: (
<>
<Markdown>
{dedent`
Exception autocapture can be enabled during initialization of the Insights client to automatically capture any exception thrown by your Angular application.
This requires overriding Angular's default \`ErrorHandler\` provider:
`}
</Markdown>
<CodeBlock
blocks={[
{
language: 'typescript',
file: 'src/app/insights-error-handler.ts',
code: dedent`
import { ErrorHandler, Injectable, Provider } from '@angular/core';
import { HttpErrorResponse } from '@angular/common/http';
import insights from 'insights-js';
@Injectable({ providedIn: 'root' })
class InsightsErrorHandler implements ErrorHandler {
public constructor() {}
public handleError(error: unknown): void {
const extractedError = this._extractError(error) || 'Unknown error';
runOutsideAngular(() => insights.captureException(extractedError));
}
protected _extractError(errorCandidate: unknown): unknown {
const error = tryToUnwrapZonejsError(errorCandidate);
if (error instanceof HttpErrorResponse) {
return extractHttpModuleError(error);
}
if (typeof error === 'string' || isErrorOrErrorLikeObject(error)) {
return error;
}
return null;
}
}
function tryToUnwrapZonejsError(error: unknown): unknown | Error {
return error && (error as { ngOriginalError: Error }).ngOriginalError
? (error as { ngOriginalError: Error }).ngOriginalError
: error;
}
function extractHttpModuleError(error: HttpErrorResponse): string | Error {
if (isErrorOrErrorLikeObject(error.error)) {
return error.error;
}
if (
typeof ErrorEvent !== 'undefined' &&
error.error instanceof ErrorEvent &&
error.error.message
) {
return error.error.message;
}
if (typeof error.error === 'string') {
return \`Server returned code \${error.status} with body "\${error.error}"\`;
}
return error.message;
}
function isErrorOrErrorLikeObject(value: unknown): value is Error {
if (value instanceof Error) {
return true;
}
if (value === null || typeof value !== 'object' || Array.isArray(value)) {
return false;
}
return 'name' in value && 'message' in value && 'stack' in value;
}
declare const Zone: any;
// eslint-disable-next-line @typescript-eslint/no-unsafe-member-access
const isNgZoneEnabled = typeof Zone !== 'undefined' && Zone.root?.run;
export function runOutsideAngular<T>(callback: () => T): T {
// eslint-disable-next-line @typescript-eslint/no-unsafe-member-access
return isNgZoneEnabled ? Zone.root.run(callback) : callback();
}
export function provideInsightsErrorHandler(): Provider {
return {
provide: ErrorHandler,
useValue: new InsightsErrorHandler(),
};
}
`,
},
]}
/>
<Markdown>
{dedent`
Then, in your \`src/app/app.config.ts\`, import the \`provideInsightsErrorHandler\` function and add it to the providers array:
`}
</Markdown>
<CodeBlock
blocks={[
{
language: 'typescript',
file: 'src/app/app.config.ts',
code: dedent`
// src/app/app.config.ts
import { ApplicationConfig, provideZoneChangeDetection } from '@angular/core';
import { provideRouter } from '@angular/router';
import { routes } from './app.routes';
import { provideInsightsErrorHandler } from './insights-error-handler'; // +
export const appConfig: ApplicationConfig = {
providers: [
...
provideInsightsErrorHandler(), // +
],
};
`,
},
]}
/>
</>
),
}
const manualCaptureStep: StepDefinition = {
title: 'Manually capture exceptions',
badge: 'optional',
content: (
<>
<Markdown>
{dedent`
If there are more errors you'd like to capture, you can manually call the \`captureException\` method:
`}
</Markdown>
<CodeBlock
blocks={[
{
language: 'typescript',
file: 'TypeScript',
code: dedent`
insights.captureException(e, additionalProperties)
`,
},
]}
/>
</>
),
}
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 [...installSteps, exceptionAutocaptureStep, manualCaptureStep, verifyStep]
}
export const AngularInstallation = createInstallation(getAngularSteps)