plea for --json for unannex and other commands
authoryarikoptic <yarikoptic@web>
Wed, 3 May 2023 19:08:03 +0000 (19:08 +0000)
committeradmin <admin@branchable.com>
Wed, 3 May 2023 19:08:03 +0000 (19:08 +0000)
doc/todo/--json_for_unannex__and_ideally_any_other_command_.mdwn [new file with mode: 0644]

diff --git a/doc/todo/--json_for_unannex__and_ideally_any_other_command_.mdwn b/doc/todo/--json_for_unannex__and_ideally_any_other_command_.mdwn
new file mode 100644 (file)
index 0000000..2f071d9
--- /dev/null
@@ -0,0 +1,4 @@
+While looking for various spots where `core.quotepath=true` is now treated by git-annex ([ref](https://github.com/datalad/datalad/pull/7372#issuecomment-1533507701)) I found that `unannex` doesn't have `--json` and we do some really ad-hoc splitting which fails with spaces and we never actually tested enough.  With all the `quotepath` and other fun, we really should get machine-readable, thus `--json`, output for all annex commands IMHO. E.g. `unannex` has recently come up within treatment of BIDS datasets, and so far we were lucky that BIDS filenames do not allow for spaces in the filenames, but there is always `derivatives/` and `sourcedata/` which are not formalized and could have all kinds of odd filenames.
+
+[[!meta author=yoh]]
+[[!tag projects/repronim]]