I decided to remove this option and to always pretty-print JSON files because it is no interest of the average user if the JSON files contain line feeds or not. The decision table is the same with or without prety-print.
The users who diff the 5dt and 5ts files (decision tables resp. test specifications) will recognize that this is only possible with pretty-printed JSON.
Pretty-print means that JSON or XML files get additional white space (line feeds and indetation) so that they can be read better by a human being. For programs reading these files the white spaces does not matter as they are ignored by specification.
Last edit: Michael Groß 2020-06-19
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I decided to remove this option and to always pretty-print JSON files because it is no interest of the average user if the JSON files contain line feeds or not. The decision table is the same with or without prety-print.
The users who diff the 5dt and 5ts files (decision tables resp. test specifications) will recognize that this is only possible with pretty-printed JSON.
Pretty-print means that JSON or XML files get additional white space (line feeds and indetation) so that they can be read better by a human being. For programs reading these files the white spaces does not matter as they are ignored by specification.
Last edit: Michael Groß 2020-06-19