5 5 | #![allow(clippy::large_enum_variant)]
|
6 6 | #![allow(clippy::wrong_self_convention)]
|
7 7 | #![allow(clippy::should_implement_trait)]
|
8 8 | #![allow(clippy::disallowed_names)]
|
9 9 | #![allow(clippy::vec_init_then_push)]
|
10 10 | #![allow(clippy::type_complexity)]
|
11 11 | #![allow(clippy::needless_return)]
|
12 12 | #![allow(clippy::derive_partial_eq_without_eq)]
|
13 13 | #![allow(clippy::result_large_err)]
|
14 14 | #![allow(clippy::unnecessary_map_on_constructor)]
|
15 + | #![allow(clippy::useless_conversion)]
|
15 16 | #![allow(clippy::deprecated_semver)]
|
16 17 | #![allow(rustdoc::bare_urls)]
|
17 18 | #![allow(rustdoc::redundant_explicit_links)]
|
18 19 | #![allow(rustdoc::broken_intra_doc_links)]
|
19 20 | #![allow(rustdoc::invalid_html_tags)]
|
20 21 | #![forbid(unsafe_code)]
|
21 22 | #![warn(missing_docs)]
|
22 23 | #![cfg_attr(docsrs, feature(doc_cfg))]
|
23 24 | //! A REST XML service that sends XML requests and responses.
|
24 25 | //!
|
25 26 | //! # Crate Organization
|
26 27 | //!
|
27 28 | //! The entry point for most customers will be [`Client`], which exposes one method for each API
|
28 29 | //! offered by the service. The return value of each of these methods is a "fluent builder",
|
29 30 | //! where the different inputs for that API are added by builder-style function call chaining,
|
30 31 | //! followed by calling `send()` to get a [`Future`](std::future::Future) that will result in
|
31 32 | //! either a successful output or a [`SdkError`](crate::error::SdkError).
|
32 33 | //!
|
33 34 | //! Some of these API inputs may be structs or enums to provide more complex structured information.
|
34 35 | //! These structs and enums live in [`types`](crate::types). There are some simpler types for
|
35 36 | //! representing data such as date times or binary blobs that live in [`primitives`](crate::primitives).
|
36 37 | //!
|
37 38 | //! All types required to configure a client via the [`Config`](crate::Config) struct live
|
38 39 | //! in [`config`](crate::config).
|
39 40 | //!
|
40 41 | //! The [`operation`](crate::operation) module has a submodule for every API, and in each submodule
|
41 42 | //! is the input, output, and error type for that API, as well as builders to construct each of those.
|
42 43 | //!
|
43 44 | //! There is a top-level [`Error`](crate::Error) type that encompasses all the errors that the
|
44 45 | //! client can return. Any other error type can be converted to this `Error` type via the
|