On Tue, Mar 14, 2017 at 11:06 PM, Stefan Bellon <sbel...@sbellon.de> wrote:
> On Mon, 13 Mar, Ross Berteig wrote: > > > When fossil is configured to include JSON support it has a fossil > > json command that consumes a JSON object full of command and > > arguments and returns a JSON object of results. A similar feature is > > available over HTTP(S) through URLs beginning with /json. > > Ah, that's why I never got JSON to work. The input to the JSON support > is via JSON object as well?! I always assumed you can just use ordinary > command line and specify something like --json to tell fossil to output > the result of the command as a JSON object. > Yes, it can accept JSON input (even from the CLI). For the full details see: https://docs.google.com/document/d/1fXViveNhDbiXgCuE7QDXQOKeFzf2qNUkBEgiUvoqFN4/view and: fossil help json doh - it seems that's missing a reference to the -json-input parameter, which expects a filename. i'll get that added. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users