샘플
Show that when NimbleCSV.define/2 receives a list for :separator, the dumper is permanently fixed to the first entry at compile time — silently rewriting output that used any alternative separator during parsing.
sha256:96745beca2a7ac60bfcc923ac4a93c445eb71335e7326488531561ca031c2f6c
PUBLISHED
L3_CONTRACT_PASS
MIT-0
케이스
- 목표
- Show that when NimbleCSV.define/2 receives a list for :separator, the dumper is permanently fixed to the first entry at compile time — silently rewriting output that used any alternative separator during parsing. HOW
- 패키지
- nimble_csv 1.3.0
- 환경
- elixir
- 생성일
- 2026-08-16T15:09:22Z
흔히 이렇게 알고 있다
When a parser is defined with separator: ["|", ";"], dumping rows that were parsed from semicolon-delimited input will preserve the semicolon separator, because the parser accepted that format.
이 샘플의 작성자가 여기서 개발자나 모델이 기대할 법한 내용으로 적어둔 것이다. 아래 계약이 실제로 실행된 것이다.
컨트랙트
- Parsing semicolon-separated CSV with a multi-separator parser succeeds, but dump_to_iodata emits pipe-separated output — the first separator in the list — not the semicolon the input used, because the dump separator is fixed at compile time by the first list entry.
- assert dumped == "alpha|beta\ngamma|delta\n"
- assert not String.contains?(dumped, ";")
파일
- NOTES.md
- csx.json
- mix.exs
- mix.lock
- test/contract.exs
검증된 아티팩트 내려받기 (tar.gz) — 컨트랙트가 실제로 실행된 바로 그 바이트
오리진 시더
검증 영수증
- elixir 1 · CONTAINER_RUN · compile:PASS · contract:PASS · load:PASS · resolve:PASS · hex@1 · 2026-08-16 · ed25519:d91480838ac982c9