Sample
Configure a tab delimiter at NimbleCSV 1.3.0 parser definition time instead of passing a parse-time separator option
sha256:e26e7d1b6ecc2ba028b74978148bdf04a5a677f286835fcb763b7c7347d24c87
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Execution evidence
Declared environment and signed verification runs are separated so you can see exactly what this sample proves.
Evidence basisSigned contract pass
Verification receipts1
Verification levelL3_CONTRACT_PASS
Declared environment
- Execution context
- elixir 1
- Operating system
- linux
- Architecture
- x64
- Runtime
- elixir 1
- Language
- elixir
- Package manager
- mix
Verification-run environments
- Execution context
- elixir 1
- Operating system
- linux alpine · musl
- Architecture
- x64
- Runtime
- elixir 1
- Language
- elixir
- Package manager
- mix
- Execution
- container · docker
CONTAINER_RUN · compile:PASS · contract:PASS · load:PASS · resolve:PASS · hex@1 · 2026-08-17
Case
- Goal
- Configure a tab delimiter at NimbleCSV 1.3.0 parser definition time instead of passing a parse-time separator option HOW
- Packages
-
nimble_csv 1.3.0
- Environment
- elixir 1
- Created
- 2026-08-17T04:44:18Z
Commonly assumed
Passing separator: "\t" to NimbleCSV.RFC4180.parse_string/2 changes that predefined parser's delimiter for the call.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert RFC4180 parse_string with separator: tab and skip_headers: false keeps each tabbed line as one field
- assert a module created by NimbleCSV.define with a tab separator splits the same input into three fields per row
Files
- NOTES.md
- csx.json
- mix.exs
- mix.lock
- test/contract_test.exs
- test/test_helper.exs
Download the source artifact (tar.gz)
Origin Seeder
csx-seed
Verification receipts
- elixir 1 · linux alpine/x64 · docker · CONTAINER_RUN · compile:PASS · contract:PASS · load:PASS · resolve:PASS · hex@1 · 2026-08-17 · ed25519:d91480838ac982c9