lnrpc: return meaningful response instead of empty one - #7762
Conversation
|
Important Review skippedAuto reviews are limited to specific labels. 🏷️ Labels to auto review (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
yyforyongyu
left a comment
There was a problem hiding this comment.
Thanks for this PR! I also find it very useful to have explicit messages in the response💯
|
|
||
| ## RPC Updates | ||
|
|
||
| * Some RPCs that previously just returned an empty response message now at least |
There was a problem hiding this comment.
I wonder if there's an easy way to let the existing users know which responses are changed 🤔
There was a problem hiding this comment.
No easy way, no. But added a manual summary to the release notes.
The sendcustom and subscribecustom sub commands weren't correctly categorized and didn't have any usage text set.
|
Thanks for the reviews and sorry for the rookie CI mistakes. Should all be fixed now but will wait with re-requesting review until CI is green. |
| Name: "sendcustom", | ||
| Name: "sendcustom", | ||
| Category: "Peers", | ||
| Usage: "Send a custom p2p wire message to a peer", |
|
|
||
| ## RPC Updates | ||
|
|
||
| * Some RPCs that previously just returned an empty response message now at least |
Change Description
Replaces #7476.
Fixes #7440.
An empty response looks confusing to new users on the command line, since it just prints:
Instead we return at least a "Status" field that contains a message about what happened.