示例
Pin Viper 1.21.0 MergeConfigMap ownership: key normalization mutates caller maps, nested maps remain aliased, and merged config stays below explicit Set
sha256:85d242441a15089921167423b815bf5dd3b843a7305bcd229f3abfe5ab1fd578
PUBLISHED
L3_CONTRACT_PASS
MIT-0
案例
- 目标
- Pin Viper 1.21.0 MergeConfigMap ownership: key normalization mutates caller maps, nested maps remain aliased, and merged config stays below explicit Set CONFIG
- 包
- github.com/spf13/viper 1.21.0
- 环境
- go 1.26
- 创建时间
- 2026-08-17T01:30:08Z
常见的想当然
MergeConfigMap treats its argument as immutable input and copies it, so changing or reusing the caller's map after the call cannot alter Viper's configuration.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- assert MergeConfigMap lowercases both top-level and nested keys in the caller-supplied maps themselves
- assert mutating the first caller-owned nested map after MergeConfigMap changes the value returned by GetString, proving that nested map was retained rather than copied
- assert a later MergeConfigMap deep-merges its replacement and new sibling into the first caller-owned nested map while also normalizing the later input in place
- assert a merge after Set changes the aliased config map underneath but GetString still returns the explicit Set value because the config rung remains lower priority
文件
- NOTES.md
- csx.json
- go.mod
- go.sum
- merge_config_map_test.go
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- go 1.26 · CONTAINER_RUN · compile:PASS · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17 · ed25519:d91480838ac982c9