I admit, when I was recently adjusting the opencsv tests to work with Java 17, this information would have been helpful, yet somehow, I failed to see that.
It would not make sense to put the column number in CsvException. Too many usages and subclasses of CsvException would never use it. Something farther down, such as CsvFieldAssignmentException or perhaps a new intermediate class in the hierarchy, would provide more fine-tuned use of the field for only the situations that need it.
I am no longer actively developing with the project, so I will leave this ticket here for anyone else who wants to tackle it. You are, of course, welcome to submit a patch yourself.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What do you consider to be the cell number? Do you mean the column number?
@aruckerjones Indeed, indeed
I admit, when I was recently adjusting the opencsv tests to work with Java 17, this information would have been helpful, yet somehow, I failed to see that.
It would not make sense to put the column number in CsvException. Too many usages and subclasses of CsvException would never use it. Something farther down, such as CsvFieldAssignmentException or perhaps a new intermediate class in the hierarchy, would provide more fine-tuned use of the field for only the situations that need it.
I am no longer actively developing with the project, so I will leave this ticket here for anyone else who wants to tackle it. You are, of course, welcome to submit a patch yourself.