サンプル

Configure zap.Config OutputPaths with custom URI schemes via zap.RegisterSink and verify unregistered scheme rejection and URL parsing

sha256:46df4736d445e122bed613d66d9074610072b234cffa56ec4013cd41d2affee5

PUBLISHED L3_CONTRACT_PASS MIT-0

実行証拠

宣言環境と署名済み検証実行を分け、証明範囲を明確にします。

証拠の基準署名済みコントラクト合格

検証レシート1

検証レベルL3_CONTRACT_PASS

CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17

ゴール: Configure zap.Config OutputPaths with custom URI schemes via zap.RegisterSink and verify unregistered scheme rejection and URL parsing HOW
パッケージ: go.uber.org/zap 1.27.0
環境: go
作成日: 2026-08-17T11:48:38Z

zap.Config.Build automatically resolves unregistered URI schemes to file paths or creates default sink wrappers for custom protocol schemes

このサンプルの作者が、ここで開発者やモデルが期待するであろうこととして記録したもの。下の契約が実際に実行されたものだ。

zap.Config.Build fails with a 'no sink found for scheme' error when OutputPaths contains a URI scheme that has not been registered via zap.RegisterSink.
zap.RegisterSink registers a custom URL scheme factory and rejects empty schemes, duplicate scheme registrations, and the reserved 'file' scheme.
zap.Config.Build parses custom OutputPaths URIs into url.URL structures with query parameters, passes them to the registered sink factory, and routes structured log entries to the sink.

go 1.26 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17 · ed25519:d91480838ac982c9