INIshell-ng

Issue 814: Cosmetic INI discrepancies

Reported by Michael Reisecker, Nov 29, 2019

In ./tests, there is a unit test for the INIParser, consequently 
showing what is currently being preserved when reading an INI file.

Some discrepancies remain between the read INI and the one we save 
back out, the biggest ones being:

1) In an effort to keep them as close as possible, if the default 
section [General] is not specified in the input file, it will not be 
written out. Currently this leads to the section header not being 
written out if there's both keys before any section, and later the 
default section found.

2) Empty sections should not be written out, unless they are already 
present in the INI file (like it is already implemented for default 
keys).

effort: 1/2 day

Comment 1 by Michael Reisecker, Nov 30, 2019

Labels: Component:UI
Relations: is related to 813

Comment 2 by Michael Reisecker, Dec 19, 2019

Nothing to do for #2, this is the default behavior.

Comment 3 by Michael Reisecker, Dec 21, 2019

Labels: Priority:Low Priority:Medium

Comment 4 by Michael Reisecker, Dec 30, 2019

3) In the long run, there should be a way to tag keys that are okay 
to have multiple times (e. g. IMPORT_BEFORE).

Created: 10 months 20 days ago by Michael Reisecker

Updated: 9 months 19 days ago

Status: New

Labels:
Priority:Low
Type:Cosmetic
Component:UI

This issue is related to
813 - Command line options