Files
klz-cables.com/.pnpm-store/v10/files/81/079b17886eddde8dea53fa9c896a700ecbe00a075884955261c58b11935c5baaeaee23a988b915b83866f509a5ced576145150192bdbe94ac362600f5cc599
Marc Mintel 5397309103
Some checks failed
Build & Deploy / 🔍 Prepare (push) Successful in 20s
Build & Deploy / 🧪 QA (push) Failing after 34s
Build & Deploy / 🏗️ Build (push) Has started running
Build & Deploy / 🚀 Deploy (push) Has been cancelled
Build & Deploy / 🧪 Smoke Test (push) Has been cancelled
Build & Deploy / ⚡ Lighthouse (push) Has been cancelled
Build & Deploy / 🔔 Notify (push) Has been cancelled
fix(products): fix breadcrumbs and product filtering (backport from main)
2026-02-24 16:04:21 +01:00

26 lines
1.1 KiB
Plaintext

import { Span as WriteableSpan, SpanKind, Tracer } from '@opentelemetry/api';
import { BasicTracerProvider, ReadableSpan } from '@opentelemetry/sdk-trace-base';
import { Scope, Span, StartSpanOptions } from '@sentry/core';
export interface OpenTelemetryClient {
tracer: Tracer;
traceProvider: BasicTracerProvider | undefined;
}
export interface OpenTelemetrySpanContext extends StartSpanOptions {
kind?: SpanKind;
}
/**
* The base `Span` type is basically a `WriteableSpan`.
* There are places where we basically want to allow passing _any_ span,
* so in these cases we type this as `AbstractSpan` which could be either a regular `Span` or a `ReadableSpan`.
* You'll have to make sure to check relevant fields before accessing them.
*
* Note that technically, the `Span` exported from `@opentelemetry/sdk-trace-base` matches this,
* but we cannot be 100% sure that we are actually getting such a span, so this type is more defensive.
*/
export type AbstractSpan = WriteableSpan | ReadableSpan | Span;
export interface CurrentScopes {
scope: Scope;
isolationScope: Scope;
}
//# sourceMappingURL=types.d.ts.map