Closed mchlrch closed 4 years ago
for columns: solution is (partially) covered by #40 , since the introduced CsvwDialectContext will preserve the order within the unused Referenceables. So within 'suppressOutput', this will be deterministic.
But: as soon as something becomes unreferenced, the order of columns will change. @mchlrch feature or bug?
But: as soon as something becomes unreferenced, the order of columns will change. @mchlrch feature or bug?
@nnamtug It's a feature. The order of the columns in the generated .csv.meta.json reflects the ordering of the PredicateObjectMapping
s. Having unreferenced columns together at the end makes sense. I prefer that behaviour over reflecting the column order from referenceables.
I consider this issue resolved and close it
To be able to effectively diff versions of generated CSVW JSON, the tableSchemas and columns need to be written in a deterministic order.