cratestack-client-rust 0.6.8

Rust-native schema-first framework for typed HTTP APIs, generated clients, and backend services.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32

//! Native Rust gRPC client runtime (ticket #209) — the `tonic` sibling of
//! `crate::client` (REST) and `crate::rpc` (RPC). Feature-gated
//! (`grpc`, off by default) so a REST/RPC-only consumer never pulls in
//! `tonic`.
//!
//! - [`core`] — [`CratestackGrpcClient`]: wraps a `tonic::client::Grpc<T>`,
//!   carries the same [`crate::auth::RequestAuthorizer`] / schema-sha
//!   conventions `crate::client::CratestackClient` (REST) and
//!   `crate::rpc::RpcClient` (RPC) already use, so a schema author
//!   configures auth once regardless of transport. Exposes one `unary`
//!   helper every generated per-model gRPC client method
//!   (`include_client_schema!`'s `grpc` codegen,
//!   `cratestack-macros::include::client::grpc`) calls into — the
//!   client-side twin of the server's hand-rolled `tonic::server::Grpc`
//!   service arms (`cratestack-macros::include::server::grpc::service`).
//! - [`error`] — [`GrpcClientError`], wrapping `tonic::Status` directly:
//!   unlike REST/RPC (which decode a JSON/CBOR error body), a gRPC error
//!   already arrives as a structured `tonic::Status` carrying the right
//!   `tonic::Code` (`cratestack_grpc::error::cool_error_to_status`
//!   already did that mapping server-side), so there is no body left to
//!   parse — see that module's doc.
//! - [`canonical`] — envelope-signing helpers mirroring
//!   `cratestack_grpc::canonical`, adapted for the client side of the
//!   wire (no frame to strip — see that module's doc for the ticket's
//!   highest-risk decision, spelled out in full).

pub mod canonical;
mod core;
mod error;

pub use core::CratestackGrpcClient;
pub use error::GrpcClientError;