Exemplo
Show that duplicate CSV headers are collapsed differently when a CSV row is converted through CSV::Row#to_h than by a generic Ruby Hash merge.
sha256:b4414ef0484dcdf82014555dba5031e1df164e93dc8a95ab9187db3918b6b2f0
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Caso
- Objetivo
- Show that duplicate CSV headers are collapsed differently when a CSV row is converted through CSV::Row#to_h than by a generic Ruby Hash merge. HOW
- Pacotes
- csv 3.3.2
- Ambiente
- ruby
- Criado
- 2026-08-16T15:27:29Z
O que costuma-se supor
A developer expects duplicated header values to follow normal Ruby Hash last-wins semantics when using CSV row conversion.
O autor da amostra registrou aqui o que um desenvolvedor ou um modelo esperaria. O contrato abaixo é o que de fato rodou.
Contrato
- CSV.parse("id,id,name\n1,2,alice\n", headers: true).first.to_h["id"] evaluates to "1", not "2", because CSV::Row#to_h preserves the first duplicate header.
- The same row converted with row.to_a.to_h returns "2" for key "id", showing that ordinary Ruby merge order rules do apply there.
Arquivos
- Gemfile
- NOTES.md
- csx.json
- 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