Beispiel

T::Props::Serializable.from_hash defaults to strict: false, silently preserving unknown payload fields in serialize rather than raising like T::Struct.new

sha256:3db2de80edf215800954a6a7c9a3ab4d24e79daf98219216191ea8bcdfa50ae2

Fall

Ziel

T::Props::Serializable.from_hash defaults to strict: false, silently preserving unknown payload fields in serialize rather than raising like T::Struct.new HOW

Pakete

sorbet-runtime 0.6.13427 minitest 5.25.4

Umgebung

ruby

Erstellt

2026-08-16T17:11:17Z

Häufige Annahme

T::Struct.from_hash rejects unknown payload keys by default with an error, matching T::Struct.new constructor validation.

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 from_hash with unset strict argument permits unknown hash keys and retains them in serialize, whereas T::Struct.new raises ArgumentError
• assert from_hash! and from_hash with strict: true raise RuntimeError when unknown keys are provided
• assert from_hash requires string keys and fails on symbol keys because keys are looked up without symbol conversion
• assert serialize defaults to strict: true, validating required properties unless explicitly relaxed

Dateien

• Gemfile
• Gemfile.lock
• NOTES.md
• csx.json
• src/account.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-16 · ed25519:d91480838ac982c9