Skip to main content

Crate taskfast_client

Crate taskfast_client 

Source
Expand description

TaskFast typed HTTP client.

The api module is generated from spec/openapi.yaml at build time by build.rs. The rewritten spec (error-alias folding) is produced in-memory via xtask::normalize_spec so the on-disk spec stays authoritative.

Use api::Client to issue requests; cross-cutting concerns (errors::Error, retry::with_backoff) live in sibling modules and will be composed over the generated client in a follow-up.

Re-exports§

pub use client::map_api_error;
pub use client::put_presigned_upload;
pub use client::ArtifactUpload;
pub use client::NetworkConfigEntry;
pub use client::NetworkConfigResponse;
pub use client::TaskFastClient;
pub use client::UserProfile;
pub use corr::record_corr;
pub use corr::record_corr_response;
pub use corr::take_last_corr;
pub use errors::Error;
pub use errors::Result;
pub use retry::with_backoff;
pub use retry::RetryPolicy;

Modules§

api
Generated typed client + DTOs for the TaskFast OpenAPI spec.
client
Authenticated TaskFast client.
corr
Server correlation-id (x-request-id) capture for the CLI trace (gh#85).
errors
Cross-cutting error type for the typed client.
retry
Retry policy and exponential-backoff driver used by crate::TaskFastClient.

Traits§

ClientInfo
Re-exported so downstream crates can call the generated client’s baseurl() / client() accessors — progenitor 0.11+ moved them off the inherent impl into this trait, which must be in scope at the call site. Interface for which an implementation is generated for all clients.

Functions§

page_limit
Convert an i64 page limit (as parsed from the CLI) into the Option<NonZeroU64> the generated client now requires: progenitor 0.14 / typify encodes the spec’s minimum: 1 in the type. Non-positive limits map to None, letting the server apply its default page size.