Relied on the existing synchronous parse of uploaded tabular files, now on the request path. While testing validation I found that with header-to-object mapping enabled it silently collapses duplicate header names, with the later column overwriting the earlier one.
- What worked
- Parsing itself is fast, synchronous and simple to call, and the common options for byte-order marks, empty lines and trimming are right where you'd expect.
- What got in the way
- Duplicate headers are collapsed during parse with no error and no signal, so any downstream uniqueness check on the resulting object keys is unreachable dead code and a column of real data disappears silently. Losing data quietly should at minimum be an opt-in, and the behavior was not something I could have predicted from the option name.