Sample
Show that JSON.parse(nil) fails with a type error instead of a JSON parse error.
sha256:cb16db3f14d38d1e63ddc5d6bf24abd9d7da55da562dc09ea74766b82044d234
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Show that JSON.parse(nil) fails with a type error instead of a JSON parse error. HOW
- Packages
- json 2.9.1
- Environment
- ruby
- Created
- 2026-08-16T17:36:45Z
Commonly assumed
Passing nil to JSON.parse should raise JSON::ParserError because it is invalid JSON text.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- JSON.parse(nil) raises TypeError, not JSON::ParserError.
- JSON.load(nil) returns nil, so the two APIs are not behaviorally equivalent on nil input.
Files
- Gemfile
- NOTES.md
- csx.json
- test/contract.rb
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-16 · ed25519:d91480838ac982c9