You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "Garren Smith (JIRA)" <ji...@apache.org> on 2015/10/06 09:40:26 UTC
[jira] [Resolved] (COUCHDB-2811) no JSON support in couch-config
[ https://issues.apache.org/jira/browse/COUCHDB-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Garren Smith resolved COUCHDB-2811.
-----------------------------------
Resolution: Fixed
> no JSON support in couch-config
> -------------------------------
>
> Key: COUCHDB-2811
> URL: https://issues.apache.org/jira/browse/COUCHDB-2811
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: nmo
> Reporter: Robert Kowalski
>
> To get the most out of nmo it supports json output for every command. this enables users to pass the `--json` flag. The json output can then get reused by them in the programming language of their choice, e.g. by spawning a childprocess of nmo in python and listening on stdout.
> Additonally: Right now there is a separation between the cli and the api commands, as the printing just happens for the cli commands, which delegate to the JS API.
> This makes the usage of the nmo JS-API a little less noisier. Users can change the loglevel of npmlog and silence it and don't get any output on stdout at all. With couch-config they will run into a lot of printing on stdout which is probably not wanted when using the API (they are interested in the result of the promises)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)