--no-stdout-logs is not working, but -n is

pouchdb / pouchdb-server

CouchDB-compatible server built on PouchDB and Node

Apache License 2.0

951 stars 154 forks source link

--no-stdout-logs is not working, but -n is #115

Open nolanlawson opened 9 years ago

nolanlawson commented 9 years ago

This seems to be a quirk of how yargs deals with the --no prefix.

marten-de-vries commented 9 years ago

https://www.npmjs.com/package/yargs#negate-fields; probably easiest to just rename the option since I don't see some option to turn it off mentioned.

nolanlawson commented 9 years ago

I'm fine with that. Since it's pre-1.0, we can do whatever we want.

How about --silent and -s?

marten-de-vries commented 9 years ago

Sounds good.

nolanlawson commented 8 years ago

Well, since we released 1.0.0 and forgot to fix this, I guess we should try to fix it so it actually works?

marten-de-vries commented 8 years ago

Absolutely. Fixing issues is more important than keeping semver versions low. PR: #126.

nolanlawson commented 7 years ago

This is still broken (-n silences successfully, but --no-stdout-logs does not), looks like we didn't fix it for some reason. I believe it was discussed but can't recall the resolution.