Currently this command immediately writes to a file, while an intuition would say that it should just print config to the console. (and actually, it was me who implemented it this way :sweat:). But okay, this has some advantages.
But this command can also overwrite the previously created config. I.e. I could create config and tune it up, then accidentally call xrefcheck dump-config again (e.g. by getting this command from history) and all my changes will be lost. This is too bad.
Acceptance criteria
dump-config does not overwrite the existing file, unless this is told explicitly (with some --force flag).
(optional) How this command outputs the config is revised.
(optional) It is possible to print the config to stdout.
Clarification and motivation
Currently this command immediately writes to a file, while an intuition would say that it should just print config to the console. (and actually, it was me who implemented it this way :sweat:). But okay, this has some advantages.
But this command can also overwrite the previously created config. I.e. I could create config and tune it up, then accidentally call
xrefcheck dump-configagain (e.g. by getting this command from history) and all my changes will be lost. This is too bad.Acceptance criteria
dump-configdoes not overwrite the existing file, unless this is told explicitly (with some--forceflag).