I’m not doing any CSV processing at the moment, but have in the past - so was interested in this thread.
@Kasper, can’t you just use #readHeader upfront, and do the assertion yourself, and then proceed to loop through your records? It would seem that the Neo caters for what you are suggesting - and if you want to add a helper method extension you have the building blocks to already do this? The only flaw I can think of, is if there is no header present then I can’t recall what Neo does - ideally throws an exception so you can decide what to do - potentially continue if the number of columns is what you expect and the data matches the columns - or you fail with an error that a header is required. But I think you would always need to do some basic initial checks when processing CSV due to the nature of the format? Tim On Fri, 22 Jan 2021, at 6:42 AM, Kasper Osterbye wrote: > As it happened, I ran into the exact same scenario as Joachim just the other > day, > that is, the external provider of my csv had added some new columns. In my > case > manifested itself in an error that an integer field was not an integer > (because new > columns were added in the middle). > > Reading through this whole thread leaves me with the feeling that no matter > what Sven > adds, there is still a risk for error. Nevertheless, my suggestion would be > to add a > functionality to #skipHeaders, or make a sister method: > #assertAndSkipHeaders: numberOfColumns onFailDo: aBlock given the actual > number of headers > That would give me a way to handle the error up front. > > This will only be interesting if your data has headers of cause. > > Thanks for NeoCSV which I use all the time! > > Best, > > Kasper
