supabase / supabase-swift / 29035534361

83%

push

github

feat(supabase): add W3C trace context propagation via OpenTelemetry trait (#1101)

* feat(supabase): add W3C trace context propagation via OpenTelemetry trait

Adds an OpenTelemetry SPM trait that pulls in opentelemetry-swift-core
directly and gates a new tracePropagation option on SupabaseClientOptions.
When enabled, the active OTel span's traceparent header is injected into
every outgoing PostgREST/Storage/Functions/Auth/Realtime request. Compiles
to a no-op when the trait is disabled, so the option is always safe to set.

Supersedes the protocol-injection approach from #1010, closed in favor of
waiting for the Swift 6.1 trait migration (SDK-1043).

Linear: SDK-1043

* fix: address code review findings for OTel trace propagation

- CI now also builds/tests with the OpenTelemetry trait enabled, so the
  trait-on code path (previously untested by any automated gate) gets
  real coverage.
- Document the two-step opt-in (dependency trait + tracePropagation)
  directly on the option, since it's the first SPM trait in this package.
- Note the pre-existing _invokeWithStreamedResponse exception so it's a
  documented gap rather than a rediscovered surprise.

* refactor: trim redundant CI step and duplicate tracing tests

- Drop the standalone "Build (OpenTelemetry trait)" CI step: the
  following test step builds the same target anyway.
- Drop injectLeavesRequestUnchangedWhenNoActiveSpan and
  activeSpanProducesMatchingTraceParentHeader: each duplicated
  coverage already provided by a sibling test at a different layer.

* refactor(supabase): drop tracePropagation flag, trait is the sole toggle

The OpenTelemetry trait already gates whether OTel is even linked, so a
separate runtime Bool was redundant dual-gating — and the exact source
of the "flag true but trait off" silent no-op a reviewer flagged
earlier. TraceContext.inject(into:) is now applied unconditionally by
SupabaseClient; it no-ops on its own whenever there's no active span
or the trait is disab... (continued)

7 of 12 new or added lines in 2 files covered. (58.33%)

7894 of 9479 relevant lines covered (83.28%)

37.66 hits per line