Exemplo
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
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Caso
- Objetivo
- T::Props::Serializable.from_hash defaults to strict: false, silently preserving unknown payload fields in serialize rather than raising like T::Struct.new HOW
- Pacotes
- sorbet-runtime 0.6.13427 minitest 5.25.4
- Ambiente
- ruby
- Criado
- 2026-08-16T17:11:17Z
O que costuma-se supor
T::Struct.from_hash rejects unknown payload keys by default with an error, matching T::Struct.new constructor validation.
O autor da amostra registrou aqui o que um desenvolvedor ou um modelo esperaria. O contrato abaixo é o que de fato rodou.
Contrato
- 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
Arquivos
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- src/account.rb
- test/contract.rb
Baixar o artefato verificado (tar.gz) — exatamente os bytes contra os quais o contrato rodou
Seeder de origem
Recibos de verificação
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-16 · ed25519:d91480838ac982c9