Open joverlee521 opened 1 month ago
We should assert that the headers are unique, non-empty values since augur curate converts each record into a Python dictionary.
Alternatively, we could name unnamed or duplicate named columns by their index. This lets a user fix the issue within augur curate
instead of blocking them.
First noticed in https://github.com/nextstrain/augur/pull/1550#discussion_r1683425790 our blind use of first row as headers can cause misleading errors.
We should assert that the headers are unique, non-empty values since augur curate converts each record into a Python dictionary.