When Csvlint is loaded into Ruby 2.5.3, it should validate valid CSV files, just like
it does in older versions of Ruby.
Current Behaviour (for problems)
What currently happens that isn't expected behaviour?
Csvlint reports :invalid_encoding for all lines. It turns out this is because it is assumed that the only reason an ArgumentError will be thrown is if there's invalid encoding.
When I commented out the rescue statements, I got this backtrace:
Expected Behaviour
When Csvlint is loaded into Ruby 2.5.3, it should validate valid CSV files, just like it does in older versions of Ruby.
Current Behaviour (for problems)
Csvlint reports
:invalid_encoding
for all lines. It turns out this is because it is assumed that the only reason anArgumentError
will be thrown is if there's invalid encoding.When I commented out the
rescue
statements, I got this backtrace:Here's how
init_converters
is being called by Ruby:Csvlint's implementation of
init_converters
only accepts 2 parameters: https://github.com/theodi/csvlint.rb/blob/master/lib/csvlint/validate.rb#L43Steps to Reproduce (for problems)
Your Environment