Beispiel

Distinguish NimbleCSV error paths where trailing characters after quotes raise unexpected escape character ParseError, unclosed quotes report expected escape character at EOF, and non-binary inputs bypass ParseError with ArgumentError or FunctionClauseError

sha256:c5a8d3d8e7491c41eec46559763ce8367d36a8dbcbeab7e5bc8d95670b4d2d09

Fall

Ziel

Distinguish NimbleCSV error paths where trailing characters after quotes raise unexpected escape character ParseError, unclosed quotes report expected escape character at EOF, and non-binary inputs bypass ParseError with ArgumentError or FunctionClauseError HOW

Pakete

nimble_csv 1.3.0

Umgebung

elixir

Erstellt

2026-08-16T15:04:55Z

Contract

• Trailing characters following a closed quote raise NimbleCSV.ParseError blaming an unexpected escape character rather than reporting unexpected trailing tokens, while unclosed quotes at EOF report expected escape character.
• assert passing non-binary collections to parse_enumerable/2 raises ArgumentError rather than NimbleCSV.ParseError
• assert passing non-binary values to parse_string/2 raises FunctionClauseError rather than NimbleCSV.ParseError
• assert NimbleCSV.ParseError struct contains only a message field and omits line, row, and column metadata
• assert invalid UTF-16 byte sequences in NimbleCSV.Spreadsheet raise generic RuntimeError rather than NimbleCSV.ParseError

Dateien

• NOTES.md
• csx.json
• mix.exs
• mix.lock
• test/contract.exs

Verifiziertes Artefakt herunterladen (tar.gz) — genau die Bytes, gegen die der Contract lief

Ursprungs-Seeder

csx-seed

Verifizierungsbelege

• elixir 1 · CONTAINER_RUN · compile:PASS · contract:PASS · load:PASS · resolve:PASS · hex@1 · 2026-08-16 · ed25519:d91480838ac982c9