Expand description
superposition_sdk
§Crate Organization
The entry point for most customers will be Client, which exposes one method for each API
offered by Superposition. The return value of each of these methods is a “fluent builder”,
where the different inputs for that API are added by builder-style function call chaining,
followed by calling send() to get a Future that will result in
either a successful output or a SdkError.
Some of these API inputs may be structs or enums to provide more complex structured information.
These structs and enums live in types. There are some simpler types for
representing data such as date times or binary blobs that live in primitives.
All types required to configure a client via the Config struct live
in config.
The operation module has a submodule for every API, and in each submodule
is the input, output, and error type for that API, as well as builders to construct each of those.
There is a top-level Error type that encompasses all the errors that the
client can return. Any other error type can be converted to this Error type via the
From trait.
The other modules within this crate are not required for normal usage.
Re-exports§
pub use client::Client;
Modules§
- client
- Client for calling Superposition.
- config
- Configuration for Superposition.
- error
- Common errors and error handling utilities.
- meta
- Information about this crate.
- operation
- All operations that this crate can perform.
- primitives
- Primitives such as
BloborDateTimeused by other types. - types
- Data structures used by operation inputs/outputs.
Structs§
- Config
- Configuration for a superposition_sdk service client.
Enums§
- Error
- All possible error types for this service.