You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently, while consuming a csv file and using readLabelled ran into .. Failed to decode XYZ: Received Field $field. This error report is partially helpful, as given a long enough CSV file this amounts to the proverbial - looking for a needle in a hay stack. It would be great if we could get something like (just a suggestion):
Row 256*. Failed to decode XYZ: Received Field $field
where 256* is the row at which the error was encountered - with or without the header column (?)
But this feature might not be that convenient for performance reasons (multi gigabyte files, lot of rows etc.) so it might need to be an opt-in feature.
So,
Can this be solved easily by client code right now? Without the need for library support.
If this were to be supported by the library how would that be?
Aside: Does the parser emit line numbers if something errors out?
The text was updated successfully, but these errors were encountered:
Recently, while consuming a csv file and using
readLabelled
ran into ..Failed to decode XYZ: Received Field $field
. This error report is partially helpful, as given a long enough CSV file this amounts to the proverbial - looking for a needle in a hay stack. It would be great if we could get something like (just a suggestion):But this feature might not be that convenient for performance reasons (multi gigabyte files, lot of rows etc.) so it might need to be an opt-in feature.
So,
Aside: Does the parser emit line numbers if something errors out?
The text was updated successfully, but these errors were encountered: