Open marianhlavac opened 2 years ago
Idea: It would also be nice to take into account different values in the CSV representing the boolean values, such as "yes", "no", 1, 0, "y", "n". While we keep the CSV consistent and we use strictly true/false, sometimes inconsistency could slip through and by making the conversion more forgiving, the CSV could be still valid and converted correctly.
Currently, all fields in JSONs, except for the boolean fields, are strings. Numeric fields should be represented as numbers.
For example, this current output:
Should look like this:
If there is a numeric value missing, it should be
null
.