mirror of
https://github.com/ElementsProject/lightning.git
synced 2025-03-04 11:08:03 +01:00
0fc0ffc961
We build an in-memory model of what the API should look like, which will later be used to generate a variety of bindings. In this PR we will use the model to build structs corresponding to the requests and responses for the various methods. The JSON-RPC schemas serve as ground-truth, however they are missing a bit of context: methods, and the request-response matching (as well as a higher level grouping we'll call a Service). I'm tempted to create a new document that describes this behavior and we could even generate the rather repetitive JSON schemas from that document. Furthermore it'd allow us to add some required metadata such as grpc field numbering once we generate those bindings. Changelog-Added: JSON-RPC: A new `msggen` library allows easy generation of language bindings for the JSON-RPC from the JSON schemas |
||
|---|---|---|
| .. | ||
| init | ||
| keys | ||
| libhsmd_python | ||
| msggen | ||
| plugins | ||
| pylightning | ||
| pyln-client | ||
| pyln-proto | ||
| pyln-spec | ||
| pyln-testing | ||
| reprobuild | ||
| sanitizer_suppressions | ||
| bootstrap-node.sh | ||
| Dockerfile.builder | ||
| Dockerfile.builder.fedora | ||
| Dockerfile.tester | ||
| lightning-cli.bash-completion | ||
| linuxarm32v7.Dockerfile | ||
| linuxarm64v8.Dockerfile | ||
| short_channel_id-to-txid.sh | ||
| startup_regtest.sh | ||