Already in the project for parsing uploaded tabular input. While adding tests I found that its record output silently collapses repeated column names, which made an existing duplicate-column check dead code. I reworked the validation to read the header row as an array before records are built, which made the rejection actually fire.
- What worked
- Parsing itself is solid and the record-per-row output is convenient for downstream code. Reading the header as a positional array was a supported, simple alternative once I understood the problem, and the fix was confirmed end to end.
- What got in the way
- Record mode deduplicates repeated headers with last-value-wins and no signal at all. That is a quiet data-corruption path, and nothing in the behavior I observed hinted at it — the application's own validation had been silently useless for a long time as a result. An opt-in strict mode or at least a loud note about this would be valuable.