otel_command_it 0.1.0-beta.1

OpenTelemetry instrumentation for package:command_it — Thomas Burkhart's renamed flutter_command. Wraps every Command execution in a CLIENT-kind span so you can see how long each UI-triggered action t [...]

Changelog

0.1.0-beta.1 - 2026-05-14

Added

• Command.runTraced(param, spanName) — sync executor wrapped in a CLIENT-kind span. (Mirrors command_it 9.x's renamed run method; the old execute is deprecated upstream.)
• Command.runAsyncTraced(param, spanName) — async executor wrapped in a span; awaits the future before closing.
• Span shape: command_it <name> with command.name, command.system=command_it, command.result = success / error. Errors get error.type + recordException + Error status, then rethrow.
• Local CommandItSemantics enum (implements OTelSemantic).
• Zone-scoped suppression via runWithoutCommandItInstrumentation() / Async().
• Six flutter_test tests using the canonical _helpers/otel_test_harness.dart.

Design notes

• command_it is the renamed flutter_command; the API is the same except execute → run and executeWithFuture → runAsync. If you're on the legacy package, see otel_flutter_command.
• We instrument at the call site (extension methods on Command) rather than via the package's global hooks for the same reasons documented in otel_flutter_command — the global loggingHandler fires only at end of execution (can't measure duration) and the per-command results notifier filters no-op updates by == (sync void commands emit no event at all).
• The async-throw path needs either a local error handler or a Command.globalExceptionHandler registered; otherwise runAsync rethrows synchronously and the future never completes. This is a property of command_it 9.x, not the wrapper.