Beispiel

Pin Viper 1.21.0 string-slice parsing differences across environment values, pflag StringSlice values, and in-memory YAML

sha256:a8a9630ca346da32b160e5e78bdd2de5b40347a27f3c473d7655f5610be6f6e7

Fall

Ziel

Pin Viper 1.21.0 string-slice parsing differences across environment values, pflag StringSlice values, and in-memory YAML HOW

Pakete

github.com/spf13/viper v1.21.0 github.com/spf13/pflag v1.0.10

Umgebung

go

Erstellt

2026-08-17T03:51:40Z

Häufige Annahme

viper.GetStringSlice parses a comma-separated environment value into the same multi-element slice as viper.Unmarshal.

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

• assert GetStringSlice returns one comma-containing element for a comma-separated environment value
• assert Unmarshal returns two elements for that same comma-separated environment value
• assert GetStringSlice splits a whitespace-separated environment value while Unmarshal retains it as one element
• assert GetStringSlice and Unmarshal both return two elements when a bound pflag.StringSlice has already parsed the comma
• assert a YAML sequence returns two elements for both APIs while a YAML comma-separated scalar remains one element in GetStringSlice and becomes two through Unmarshal

Dateien

• NOTES.md
• csx.json
• go.mod
• go.sum
• slice_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