Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typos and rpc help text #2120

Merged
merged 9 commits into from
Jun 18, 2018
Merged

Conversation

UdjinM6
Copy link

@UdjinM6 UdjinM6 commented Jun 13, 2018

Cleanup only, no functionality/actual code changes.

Changes:

  • fix few typos and corresponding translations (a better version of Typo in PrivateSend info. #2111 );
  • clarify/unify/fix some rpc help text (I believe there were some forum posts mentioning them or smth like that but can't find these now).

If you know of any other similar things, pls leave your comment below, let's collect them all here and fix at once.

@@ -1304,7 +1304,7 @@ UniValue listreceivedbyaddress(const JSONRPCRequest& request)
if (request.fHelp || request.params.size() > 4)
throw std::runtime_error(
"listreceivedbyaddress ( minconf addlockconf include_empty include_watchonly)\n"
"\nList balances by receiving address.\n"
"\nList recieves by receiving address.\n"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sp. - receives

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ohhh 🙈

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, did this need to be changed? It does list the balance by address, right?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, I'm not sure "List receives by ..." makes sense (at least not to me).

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this matches what it does. What do you guys think?
"List transactions received by an address."

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wait, so it's not specifying the tx outpoint, meaning if you get this list, then it's up to you to query the transaction and determine which output(s) paid to the address?

I'm also curious how confirmations is used here... is this the number of confirmations of the latest transaction with some number of outputs which pays out to this address?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nmarley Yes, that sounds correct. And the confirmation count is for the latest tx. I finally looked it up on this super helpful site 😆

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, well whatever sounds good to you then. Seems like a funny call which only points in the right direction instead of serving fully useful info, but that's another issue entirely.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe List incoming payments grouped by receiving address and List incoming payments grouped by account? Should be clear enough.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Sounds okay to me. That describes what they do.

@@ -882,7 +882,7 @@ UniValue sendrawtransaction(const JSONRPCRequest& request)
"1. \"hexstring\" (string, required) The hex string of the raw transaction)\n"
"2. allowhighfees (boolean, optional, default=false) Allow high fees\n"
"3. instantsend (boolean, optional, default=false) Use InstantSend to send this transaction\n"
"3. bypasslimits (boolean, optional, default=false) Bypass transactions policy limits\n"
"4. bypasslimits (boolean, optional, default=false) Bypass transactions policy limits\n"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit - "Bypass transaction policy limits".
Maybe? 🙂

Copy link
Collaborator

@thephez thephez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🏁

Copy link

@nmarley nmarley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK, LGTM

@UdjinM6 UdjinM6 added this to the 12.3 milestone Jun 16, 2018
@UdjinM6 UdjinM6 merged commit 5669fc8 into dashpay:develop Jun 18, 2018
andvgal pushed a commit to energicryptocurrency/gen2-energi that referenced this pull request Jan 6, 2019
* Fix typo in PS info dialog

Also adjust translations accordingly.

* Fix typo in PS low key warning

* Fix typo in sendrawtransaction help

* Fix sendtoaddress/sendmany help text

* Fix listreceivedby* help text

* Fix typo in listunspent help

* Fix spelling "recieves"->"receives"

Shame on me

* transactions->transaction

* receives->"incoming payments grouped"
@UdjinM6 UdjinM6 deleted the fixtyposandtext branch November 26, 2020 13:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants