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
I noticed that when you have a custom type with custom converter using UnmarshalCSV, if it has an error, the Reader bails out from reading the rest of the rows, and they all become nil. Instead of bailing out, could we have an option where the reader will just return that row as nil but then continue on? So that way it doesn't nil-out valid rows. Let me know if that doesn't make sense.
The text was updated successfully, but these errors were encountered:
I noticed that when you have a custom type with custom converter using
UnmarshalCSV
, if it has an error, the Reader bails out from reading the rest of the rows, and they all becomenil
. Instead of bailing out, could we have an option where the reader will just return that row as nil but then continue on? So that way it doesn't nil-out valid rows. Let me know if that doesn't make sense.The text was updated successfully, but these errors were encountered: