nimbus-eth2/beacon_chain/spec/eth2_apis/rpc_node_calls.nim
Jacek Sieka 3d7bee8502
REST API client, JSON-RPC cleanups (#2756)
This refactoring puts the JSON-RPC and REST APIs on more equal footing
by renaming and moving things around, creating a separation between
client and server, and documenting what they are - the aim is to have a
simple-to-use base to start from when developing API clients, as well as
make it easier to navigate the code when looking for the legacy JSON-RPC
interface vs the new REST API.

* move REST client, serialization and supporting types to spec/eth2_apis
* REST stuff now starts with `rest_`, JSON-RPC stuff starts with `rpc_`,
more or less
* simplify imports such that there's a simple module to import for both
server and client
* map REST type and proc names to yaml spec more closely - in
particular, reuse operation and type names in `rest_types` to make
comparisons against spec more easy
* cleaner separation between client and server modules - modules common
between server and client such as `rest_types` and serialization move to
the spec folder - this allows the client to be built with less knowledge
about server internals
2021-08-03 17:17:11 +02:00

12 lines
314 B
Nim

import
options,
rpc_types
proc get_v1_node_identity(): RpcNodeIdentity
proc get_v1_node_version(): JsonNode
proc get_v1_node_syncing(): RpcSyncInfo
proc get_v1_node_health(): JsonNode
proc get_v1_node_peers(state: Option[seq[string]],
direction: Option[seq[string]]): seq[RpcNodePeer]