Exemplo
Demonstrate that turning on `return_headers` changes how header columns are surfaced when `headers: true` is also enabled.
sha256:3d12db62adbd2a7953f464fa2bbaaffa6d87ba0e99054b30dad1404f2b997473
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Caso
- Objetivo
- Demonstrate that turning on `return_headers` changes how header columns are surfaced when `headers: true` is also enabled. HOW
- Pacotes
- csv 3.3.2
- Ambiente
- ruby
- Criado
- 2026-08-16T15:29:58Z
O que costuma-se supor
A parser configured with `headers: true` still makes column lookups expose only data rows, so the header names are never treated as a data value.
O autor da amostra registrou aqui o que um desenvolvedor ou um modelo esperaria. O contrato abaixo é o que de fato rodou.
Contrato
- assert CSV.parse("id,name\n1,alice\n2,bob\n", headers: true, return_headers: true)["name"] == ["name", "alice", "bob"]
- assert CSV.parse("id,name\n1,alice\n2,bob\n", headers: true)["name"] == ["alice", "bob"]
- assert CSV.parse("id,name\n1,alice\n", headers: true, return_headers: true).first.to_a == ["id", "name"]
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