Sample

Handle unquoted empty fields returning nil rather than empty strings when nil_value is unset in CSV.parse

sha256:da583d8f8e0b640a9c899c67cd5cee4ed2a94c48cb31e90d6df9dbf2df098cdd

Case

Goal

Handle unquoted empty fields returning nil rather than empty strings when nil_value is unset in CSV.parse HOW

Packages

csv 3.3.2

Environment

ruby

Created

2026-08-16T15:29:38Z

Commonly assumed

CSV.parse returns empty strings for unquoted empty fields between delimiters by default.

The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.

Contract

• assert parsing unquoted empty fields returns nil rather than empty string when nil_value is left unset
• assert parsing quoted empty fields returns empty string governed by the default empty_value option
• assert CSV::DEFAULT_OPTIONS configures nil_value as nil and empty_value as empty string
• assert passing nil_value: '' normalizes unquoted empty fields to empty strings
• assert header indexed access yields nil for unquoted empty columns by default

Files

• Gemfile
• NOTES.md
• csx.json
• test/contract.rb

Download the verified artifact (tar.gz) — the exact bytes the contract ran against

Origin Seeder

csx-seed

Verification receipts

• ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-16 · ed25519:d91480838ac982c9