Skip to main content

Crate todoku

Crate todoku 

Source
Expand description

Todoku (届く) — Shared authenticated HTTP client with retry and JSON deserialization.

Wraps reqwest so every pleme-io app with API calls uses the same builder pattern, pluggable auth, and exponential-backoff retry.

Re-exports§

pub use auth::Auth;
pub use auth::BasicAuth;
pub use auth::BearerToken;
pub use auth::HeaderAuth;
pub use auth::NoAuth;
pub use blocking::BlockingHttpClient;
pub use blocking::HttpResponse;
pub use client::HttpClient;
pub use client::HttpClientBuilder;
pub use credentials::CredentialError;
pub use credentials::CredentialTable;
pub use credentials::OwnerEntry;
pub use credentials::Resolution;
pub use credentials::Token;
pub use credentials::owner_from_remote_url;
pub use credentials::owner_from_repo_arg;
pub use error::TodokuError;
pub use github::FileInfo;
pub use github::GitHubApi;
pub use github::GitHubClient;
pub use github::GitHubRepo;
pub use github::OwnerType;
pub use retry::Idempotency;
pub use retry::Jitter;
pub use retry::RetryError;
pub use retry::RetryPolicy;
pub use retry::RetryVerdict;
pub use retry::entropy;
pub use retry::parse_retry_after;
pub use retry::retry_with_backoff;
pub use retry::retry_with_verdict;
pub use ssrf::SsrfReason;
pub use ssrf::check_url;
pub use ssrf::classify_ip;
pub use tls::TlsProfile;

Modules§

auth
Pluggable authentication strategies for HTTP requests.
blocking
Blocking (synchronous) HTTP facade over the async HttpClient.
client
Core HTTP client with authentication, retry, and JSON deserialization.
credentials
Owner-scoped GitHub credential resolution.
error
Error types for the todoku HTTP client.
github
GitHub API client built on todoku’s HttpClient.
retry
Configurable retry policies with exponential backoff.
ssrf
SSRF (Server-Side Request Forgery) protection — a typed, pure-Rust guard.
tls
Typed TLS-fingerprint profiles for the HTTP client.