Beispiel

Distinguish JSON.parse! relaxed parsing from JSON.parse strict limits, load explicit json/add core additions for bidirectional serialization, and forward generator State through custom to_json methods

sha256:bc062acc906536678976cf1c339f352acd1b7ab93a8126083d2e995f58c8816b

Fall

Ziel

Distinguish JSON.parse! relaxed parsing from JSON.parse strict limits, load explicit json/add core additions for bidirectional serialization, and forward generator State through custom to_json methods HOW

Pakete

json 2.9.1

Umgebung

ruby

Erstellt

2026-08-17T02:43:07Z

Häufige Annahme

JSON.parse! is an exception-raising strict mode of JSON.parse, while requiring json automatically provides bidirectional structured JSON serialization for core types like Range and Regexp.

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 JSON.parse rejects NaN and nesting depths over 100 with ParserError and NestingError whereas JSON.parse! relaxes limits to allow NaN and unbounded nesting by default
• assert core types like Range, Regexp, Complex, and Rational require explicit json/add modules to serialize as json_class additions and reconstruct via create_additions
• assert JSON.generate passes a JSON::State instance to custom to_json methods raising ArgumentError on arity-zero definitions unless state arguments are forwarded
• assert JSON::State enables custom whitespace and ASCII formatting while pretty_generate formats with newlines and fast_generate bypasses depth checks

Dateien

• Gemfile
• Gemfile.lock
• NOTES.md
• csx.json
• src/json_protocol.rb
• test/contract.rb

Verifiziertes Artefakt herunterladen (tar.gz) — genau die Bytes, gegen die der Contract lief

Ursprungs-Seeder

csx-seed

Verifizierungsbelege

• ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9