claude/issue-519-011CUNA6yBcZ6jGqWMSD2gan - Branch - kamiazya/web-csv-toolbox

Add rowNumber field to ParseError for better error reporting

#539

Comparing

claude/issue-519-011CUNA6yBcZ6jGqWMSD2gan

(

d93f88b

) with

main

(

009c762

)

-1%

Untouched: 7

Benchmarks

Passed

parseBinary.toStream(50 rows)

benchmark/main.ts

+4%

1.1 ms1.1 ms

parseString.toStream(50 rows)

benchmark/main.ts

+2%

1.1 ms1.1 ms

parseStringToArraySyncWASM(50 rows)

benchmark/main.ts

643.6 µs642.7 µs

parseBinary.toArraySync(50 rows)

benchmark/main.ts

-1%

523 µs526 µs

parseString.toArraySync(50 rows)

benchmark/main.ts

-1%

506.5 µs509.5 µs

parseString.toIterableIterator(50 rows)

benchmark/main.ts

-1%

569.8 µs574.5 µs

parseBinary.toIterableIterator(50 rows)

benchmark/main.ts

-8%

511 µs558.1 µs

Commits

Click on a commit to change the comparison range

Base

main

009c762

-0.64%

Add rowNumber field to ParseError for better error reporting This commit adds a rowNumber field to the ParseError class to make it easier for users to identify which CSV record failed during parsing. Changes: - Add rowNumber field to ParseErrorOptions interface and ParseError class - Update Lexer to include rowNumber when throwing ParseError - Add unit tests for rowNumber property - Add integration test verifying rowNumber is set correctly on parse errors The rowNumber field provides more intuitive error messages compared to line numbers, especially when CSV files contain multi-line quoted fields. Fixes #519 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>

d93f88b

13 hours ago

by claude

Home Terms Privacy Docs