Creating https://github.com/SergelsOrg/csv2tex/issues/64 I realized that there are not just hidden assumptions in the placeholder code, but also things about the CSV format that should be documented in README.md.
While the CSV handling has good error messages that will point the user exactly to what they need to change in their data if anything is not working, they will surely want to know beforehand.
[x] Document the CSV structure (which columns are positional parameters, what other columns exist)
[x] Document current assumptions about content (e.g., grades "1", "2", "3", "4", but not beyond that)
Technically, that is part of the replacement algorithm :thinking:
Creating https://github.com/SergelsOrg/csv2tex/issues/64 I realized that there are not just hidden assumptions in the placeholder code, but also things about the CSV format that should be documented in
README.md.While the CSV handling has good error messages that will point the user exactly to what they need to change in their data if anything is not working, they will surely want to know beforehand.
Maybe, should be done after https://github.com/SergelsOrg/csv2tex/issues/58 - because it will introduce some more changes to the data format.