harper
https://github.com/automattic/harper
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
not yet supported1 Subscribers
Add a CodeTriage badge to harper
Help out
- Issues
- bitcoind (Bitcoind is the Bitcoin daemon, a command-line interface for interacting with the Bitcoin network. It allows users to run a full Bitcoin node, manage wallets, and send or receive transactions) marked as spelling issue.
- bitcoin-cli (bitcoin-cli is a command-line interface for interacting with the Bitcoin Core software, allowing users to manage wallets, query blockchain data, and perform transactions) marked as spelling problem
- -rpcwallet= (bitcoin-cli when a -rpcwallet= parameter is passed in. In this context) marked as spelling problem
- args (all RPC methods accept a named parameter called args, which can be set to an array of initial positional values that are combined with named values) marked as style problem
- getnetworkinfo (This makes the RPC interface implicitly versioned on the major version. The version tuple can be retrieved by e.g. the getnetworkinfo RPC in version) marked as spelling problem
- -deprecatedrpc= (Usually deprecated features can be re-enabled during the grace-period of one major version via the -deprecatedrpc= command line option) marked as spelling problem
- v2.0 (The server recognizes JSON-RPC v2.0 requests and responds accordingly. In this context) marked as spelling problem
- "jsonrpc": "2.0" (A 2.0 request is identified by the presence of "jsonrpc": "2.0" in the request body. In this context) marked as spelling problem
- v1.1 (If that key + value is not present in a request, the legacy JSON-RPC v1.1 protocol is followed instead, which was the only available protocol in v27.0 and prior releases. In this context) marked as spelling issue
- v27.0 (If that key + value is not present in a request, the legacy JSON-RPC v1.1 protocol is followed instead, which was the only available protocol in v27.0 and prior releases. In this context) marked as spelling problem
- Docs
- not yet supported