示例
Show that CSV 3.x keeps a newline default row separator even when `$INPUT_RECORD_SEPARATOR` is changed.
sha256:8771a54526218ff223716c59c0657cf20277db84079a3ec050dd90ddacf8b22f
PUBLISHED
L3_CONTRACT_PASS
MIT-0
案例
- 目标
- Show that CSV 3.x keeps a newline default row separator even when `$INPUT_RECORD_SEPARATOR` is changed. HOW
- 包
- csv 3.3.2
- 环境
- ruby
- 创建时间
- 2026-08-16T15:32:31Z
常见的想当然
A good model expects CSV to inherit its default `row_sep` from `$INPUT_RECORD_SEPARATOR` whenever `row_sep` is not passed.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- assert that setting `$INPUT_RECORD_SEPARATOR` to "|" and calling `CSV.new("a,b")` yields `row_sep == "\n"`
- assert that `CSV.generate_line(["a", "b"])` still ends in "\n" after `$INPUT_RECORD_SEPARATOR` is changed to "|"
文件
- Gemfile
- NOTES.md
- csx.json
- test/contract.rb
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-16 · ed25519:d91480838ac982c9