示例
Preserve Ruby object and key types across JSON serialization boundaries without falling into as_json omission, symbolize_names and create_additions incompatibility, or silent key collision data loss
sha256:274b26e9f2c0a58c7a444f4d62e6bb7ca665c0f5f1069a445b9faa8adecd8b4d
PUBLISHED
L3_CONTRACT_PASS
MIT-0
案例
- 目标
- Preserve Ruby object and key types across JSON serialization boundaries without falling into as_json omission, symbolize_names and create_additions incompatibility, or silent key collision data loss HOW
- 包
- json 2.9.1
- 环境
- ruby
- 创建时间
- 2026-08-16T17:36:59Z
常见的想当然
JSON.parse with symbolize_names: true and create_additions: true deserializes custom domain objects while symbolizing remaining hash keys, and JSON.generate serializes objects that implement as_json.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- assert JSON.parse raises ArgumentError when :symbolize_names and :create_additions are combined, making addition deserialization mutually exclusive with key symbolization
- assert JSON.generate ignores as_json and serializes arbitrary objects to inspect strings unless to_json is defined, while a to_json returning a Hash raises TypeError
- assert JSON.parse with create_additions: true instantiates registered domain objects via json_create, whereas custom create_id mismatch or missing json_create returns a plain Hash and uninitialized classes raise ArgumentError
- assert JSON.generate stringifies non-string hash keys where nil becomes an empty string, and colliding stringified keys silently overwrite earlier values on parse
- assert core Ruby types like Range and Symbol require json/add extensions to encode json_class structures, which default JSON.parse reads as Hash and create_additions: true restores to exact instances
文件
- Gemfile
- NOTES.md
- csx.json
- src/type_boundary.rb
- test/contract.rb
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-16 · ed25519:d91480838ac982c9