Closed rufuspollock closed 9 years ago
I can reproduce. Will fix over next 24 hours.
Bug is fixed.
@pwalsh what was the bug?
The bug was an unhandled case where column names in the data are not found in the schema (admittedly, this is likely to be common and should have been covered by tests earlier).
In this case, we correctly write an error when looking at data headers, but when iterating rows, the code was still trying to work with a jtskit.models.SchemaModel
instance using data (column names) that the schema model doesn't know about.
jtskit does the right thing (return None) but goodtables did not do the right thing (never expected a None).
Steps to reproduce: