The INI file
[section1] key1=v1 key2=v2 [section2] key3=v3 key4=v4 [section1] key5=v5 key6=v6
should cause a parser error.
Fields changed
description: The INI file
should cause a parser error. => The INI file {{{ [section1] key1=v1 key2=v2 [section2] key3=v3 key4=v4 [section1] key5=v5 key6=v6 }}} should cause a parser error.
Alternatively we should at least provide an argument that would tell what to do with it but it seems to be a bit of over-engineering. Thoughts?
Duplicate session names should probably have an option to fail, merge or replace.
Replying to [comment:3 sgallagh]:
This is fine. It makes sense then to use the same options in the merge call too. But I suggest the following options: - Fail - Merge (try to combine the two following the merge rules for the section - probably default) - Replace the whole section - Preserve the first and drop the new one
milestone: NEEDS_TRIAGE => Tools 1.0
rhbz: => 0
This is a part of the merge logic that needs to be released in 1.0.
blockedby: => blocking: => coverity: => feature_milestone: => milestone: Tools Backlog => Tools 1.0 patch: => 0
Patches have been pushed.
design: => design_review: => 0 fedora_test_page: => resolution: => fixed status: new => closed
Metadata Update from @dpal: - Issue assigned to dpal - Issue set to the milestone: Tools 1.0