mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

factor out maybeAddJSONField

Browse source 
Sponsored-By: the NIH-funded NICEMAN (ReproNim TR&D3) project
This commit is contained in:
Joey Hess 2023-05-08 16:03:34 -04:00
parent 3d8f93dc0a
commit a5d0c85ae1
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
6 changed files with 22 additions and 18 deletions
Download patch file Download diff file Expand all files Collapse all files

9
doc/todo/--json_for_unannex__and_ideally_any_other_command_.mdwn
View file

@ -45,7 +45,6 @@ Provisional list of commands that don't support --json and maybe should:
* git-annex-initremote
* git-annex-merge
* git-annex-renameremote
* git-annex-sync
* git-annex-upgrade
These commands could support json, but I punted:
@ -113,3 +112,11 @@ These commands have been reviewed and should not support json:
(no output that would be useful to a program using these. They enter a
new branch and git branch will tell what it is.)
* git-annex-inprogress (output is already machine readable)
* git-annex-sync (while it would be pretty easy to support, it outputs
different types of messages depending on what remotes it syncs with and
what needs to be done. Eg, copy to remote, or export to remote, or import
from remote. Each would be a different format of json message, which
violates the principle that all git-annex json output should be
discoverable by simply running the command. And of course, everything it
does can be done by other commands, which can support json without having
that problem.)