Consistency fixes for RPC descriptions #14373
pull ch4ot1c wants to merge 1 commits into bitcoin:master from ch4ot1c:fix/rpc-descriptions changing 5 files +38 −38-
ch4ot1c commented at 8:16 pm on October 2, 2018: contributor
-
in src/rpc/blockchain.cpp:512 in 25cc47c8f4 outdated
508@@ -509,17 +509,17 @@ static UniValue getmempoolancestors(const JSONRPCRequest& request) 509 { 510 if (request.fHelp || request.params.size() < 1 || request.params.size() > 2) { 511 throw std::runtime_error( 512- "getmempoolancestors txid (verbose)\n" 513+ "getmempoolancestors txid ( verbose )\n"
practicalswift commented at 8:50 pm on October 2, 2018:What is the original rationale behind the spacing in( verbose )
?
ch4ot1c commented at 9:03 pm on October 2, 2018:Unsure. Maybe to differentiate it from other normal options. It was also done with( verbosity )
, so I matched it. -
fanquake added the label RPC/REST/ZMQ on Oct 2, 2018
-
jimmysong commented at 4:20 am on October 3, 2018: contributorIt would be nice to get all the capitalizations consistent as well. Sometimes the description for a hash result will say “The block hash” others will say “the block hash”.
-
MarcoFalke commented at 4:33 am on October 3, 2018: memberThe formatting fixes would be more elegantly solved with a helper class that takes care of the formatting: See #14378
-
DrahtBot commented at 6:57 am on October 4, 2018: member
Coverage Change (pull 14373) Reference (master) Lines -0.0463 % 87.0471 % Functions +0.0000 % 84.1130 % Branches -0.0322 % 51.5403 % -
ch4ot1c commented at 8:11 pm on October 7, 2018: contributor
Also:
- First letter capitalization consistency
- Final
.
consistency
should be added to the docgen / its checker
-
fanquake commented at 7:13 am on October 9, 2018: memberPlease squash your commits, and we can merge this in. Moving forward we’re likely to be generating this kind of documentation, so that styling can remain consistent.
-
ch4ot1c force-pushed on Oct 9, 2018
-
[rpc] Descriptions: Textual consistency fixes
'Must be one of' should always end in a ':' 'hex encoded' is now always 'hex-encoded' Remove redundant '(defaults to CONSERVATIVE)' text from estimatesmartfee Consistent spacing for options '( verbose )' and '( verbosity )' 'BIP125 replaceable' is now always 'BIP125-replaceable' JSON-RPC example is now always 'As a JSON-RPC call'
-
ch4ot1c force-pushed on Oct 9, 2018
-
ch4ot1c commented at 1:44 pm on October 9, 2018: contributorSquashed
-
fanquake commented at 0:44 am on October 10, 2018: memberutACK b8edb98
-
meshcollider commented at 1:00 am on October 10, 2018: contributor
-
promag commented at 1:05 am on October 10, 2018: memberIt would be nice to have a plan for this consistency/cleanup/format etc. There is nothing in place to prevent adding the same inconsistencies. As it is I’m -0.
-
meshcollider commented at 1:25 am on October 10, 2018: contributor
-
fanquake added this to the "Mergeable" column in a project
-
MarcoFalke merged this on Oct 10, 2018
-
MarcoFalke closed this on Oct 10, 2018
-
MarcoFalke referenced this in commit be992701b0 on Oct 10, 2018
-
promag commented at 10:59 am on October 10, 2018: memberAlrighty then 👍
-
promag commented at 11:58 am on October 10, 2018: memberMissed
"listtransactions (dummy count skip include_watchonly)\n"
? -
fanquake removed this from the "Mergeable" column in a project
-
deadalnix referenced this in commit 9d64eabb34 on Mar 20, 2020
-
ftrader referenced this in commit 72a527512d on May 19, 2020
-
Munkybooty referenced this in commit 6c654d07a2 on Jul 21, 2021
-
Munkybooty referenced this in commit 8b9438c406 on Jul 21, 2021
-
Munkybooty referenced this in commit 6862fe4031 on Jul 22, 2021
-
Munkybooty referenced this in commit 938be4b3eb on Jul 22, 2021
-
Munkybooty referenced this in commit 2284dd01a2 on Jul 23, 2021
-
DrahtBot locked this on Sep 8, 2021