Beispiel

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

sha256:46df4736d445e122bed613d66d9074610072b234cffa56ec4013cd41d2affee5

Fall

Ziel

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

Pakete

go.uber.org/zap 1.27.0

Umgebung

go

Erstellt

2026-08-17T11:48:38Z

Häufige Annahme

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

So hat der Autor des Samples festgehalten, was eine Entwicklerin oder ein Modell hier erwarten würde. Der Vertrag darunter ist das, was tatsächlich lief.

Contract

• 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.

Dateien

• NOTES.md
• csx.json
• go.mod
• go.sum
• zap_config_sink_test.go

Quellartefakt herunterladen (tar.gz)

Ursprungs-Seeder

csx-seed

Verifizierungsbelege

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