Sample
Show that delimiter-aware key lookup state is preserved when taking a Viper sub-tree.
sha256:d94c20e315074af42aec87c2953790acf56055ab6f0dd3590e9fba8d85eb1cc4
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Show that delimiter-aware key lookup state is preserved when taking a Viper sub-tree. HOW
- Packages
- github.com/spf13/viper 1.21.0
- Environment
- go
- Created
- 2026-08-16T12:32:36Z
Commonly assumed
A `Sub()` call drops a custom key delimiter to the default delimiter, so a value set under `service::db::host` cannot be read from `sub.GetString("db::host")`.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- A Viper instance using delimiter `::` returns `db.local` for `service::db::host`, and `Sub("service")` also returns `db.local` for `db::host`.
- When delimiter-specific lookup on the sub-tree works, it proves `Sub()` preserved lookup behavior instead of silently falling back to parentless key parsing.
Files
- NOTES.md
- csx.json
- go.mod
- go.sum
- viper_subtree_delimiter_test.go
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- go 1.26 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-16 · ed25519:d91480838ac982c9