google_vision1/lib.rs
1// DO NOT EDIT !
2// This file was generated automatically from 'src/generator/templates/api/lib.rs.mako'
3// DO NOT EDIT !
4
5//! This documentation was generated from *Vision* crate version *7.0.0+20251212*, where *20251212* is the exact revision of the *vision:v1* schema built by the [mako](http://www.makotemplates.org/) code generator *v7.0.0*.
6//!
7//! Everything else about the *Vision* *v1* API can be found at the
8//! [official documentation site](https://cloud.google.com/vision/).
9//! The original source code is [on github](https://github.com/Byron/google-apis-rs/tree/main/gen/vision1).
10//! # Features
11//!
12//! Handle the following *Resources* with ease from the central [hub](Vision) ...
13//!
14//! * files
15//! * [*annotate*](api::FileAnnotateCall) and [*async batch annotate*](api::FileAsyncBatchAnnotateCall)
16//! * [images](api::Image)
17//! * [*annotate*](api::ImageAnnotateCall) and [*async batch annotate*](api::ImageAsyncBatchAnnotateCall)
18//! * locations
19//! * [*operations get*](api::LocationOperationGetCall)
20//! * [operations](api::Operation)
21//! * [*cancel*](api::OperationCancelCall), [*delete*](api::OperationDeleteCall), [*get*](api::OperationGetCall) and [*list*](api::OperationListCall)
22//! * projects
23//! * [*files annotate*](api::ProjectFileAnnotateCall), [*files async batch annotate*](api::ProjectFileAsyncBatchAnnotateCall), [*images annotate*](api::ProjectImageAnnotateCall), [*images async batch annotate*](api::ProjectImageAsyncBatchAnnotateCall), [*locations files annotate*](api::ProjectLocationFileAnnotateCall), [*locations files async batch annotate*](api::ProjectLocationFileAsyncBatchAnnotateCall), [*locations images annotate*](api::ProjectLocationImageAnnotateCall), [*locations images async batch annotate*](api::ProjectLocationImageAsyncBatchAnnotateCall), [*locations operations get*](api::ProjectLocationOperationGetCall), [*locations product sets add product*](api::ProjectLocationProductSetAddProductCall), [*locations product sets create*](api::ProjectLocationProductSetCreateCall), [*locations product sets delete*](api::ProjectLocationProductSetDeleteCall), [*locations product sets get*](api::ProjectLocationProductSetGetCall), [*locations product sets import*](api::ProjectLocationProductSetImportCall), [*locations product sets list*](api::ProjectLocationProductSetListCall), [*locations product sets patch*](api::ProjectLocationProductSetPatchCall), [*locations product sets products list*](api::ProjectLocationProductSetProductListCall), [*locations product sets remove product*](api::ProjectLocationProductSetRemoveProductCall), [*locations products create*](api::ProjectLocationProductCreateCall), [*locations products delete*](api::ProjectLocationProductDeleteCall), [*locations products get*](api::ProjectLocationProductGetCall), [*locations products list*](api::ProjectLocationProductListCall), [*locations products patch*](api::ProjectLocationProductPatchCall), [*locations products purge*](api::ProjectLocationProductPurgeCall), [*locations products reference images create*](api::ProjectLocationProductReferenceImageCreateCall), [*locations products reference images delete*](api::ProjectLocationProductReferenceImageDeleteCall), [*locations products reference images get*](api::ProjectLocationProductReferenceImageGetCall), [*locations products reference images list*](api::ProjectLocationProductReferenceImageListCall) and [*operations get*](api::ProjectOperationGetCall)
24//!
25//!
26//!
27//!
28//! Not what you are looking for ? Find all other Google APIs in their Rust [documentation index](http://byron.github.io/google-apis-rs).
29//!
30//! # Structure of this Library
31//!
32//! The API is structured into the following primary items:
33//!
34//! * **[Hub](Vision)**
35//! * a central object to maintain state and allow accessing all *Activities*
36//! * creates [*Method Builders*](common::MethodsBuilder) which in turn
37//! allow access to individual [*Call Builders*](common::CallBuilder)
38//! * **[Resources](common::Resource)**
39//! * primary types that you can apply *Activities* to
40//! * a collection of properties and *Parts*
41//! * **[Parts](common::Part)**
42//! * a collection of properties
43//! * never directly used in *Activities*
44//! * **[Activities](common::CallBuilder)**
45//! * operations to apply to *Resources*
46//!
47//! All *structures* are marked with applicable traits to further categorize them and ease browsing.
48//!
49//! Generally speaking, you can invoke *Activities* like this:
50//!
51//! ```Rust,ignore
52//! let r = hub.resource().activity(...).doit().await
53//! ```
54//!
55//! Or specifically ...
56//!
57//! ```ignore
58//! let r = hub.files().async_batch_annotate(...).doit().await
59//! let r = hub.images().async_batch_annotate(...).doit().await
60//! let r = hub.locations().operations_get(...).doit().await
61//! let r = hub.operations().cancel(...).doit().await
62//! let r = hub.operations().delete(...).doit().await
63//! let r = hub.operations().get(...).doit().await
64//! let r = hub.operations().list(...).doit().await
65//! let r = hub.projects().files_async_batch_annotate(...).doit().await
66//! let r = hub.projects().images_async_batch_annotate(...).doit().await
67//! let r = hub.projects().locations_files_async_batch_annotate(...).doit().await
68//! let r = hub.projects().locations_images_async_batch_annotate(...).doit().await
69//! let r = hub.projects().locations_operations_get(...).doit().await
70//! let r = hub.projects().locations_product_sets_import(...).doit().await
71//! let r = hub.projects().locations_products_purge(...).doit().await
72//! let r = hub.projects().operations_get(...).doit().await
73//! ```
74//!
75//! The `resource()` and `activity(...)` calls create [builders][builder-pattern]. The second one dealing with `Activities`
76//! supports various methods to configure the impending operation (not shown here). It is made such that all required arguments have to be
77//! specified right away (i.e. `(...)`), whereas all optional ones can be [build up][builder-pattern] as desired.
78//! The `doit()` method performs the actual communication with the server and returns the respective result.
79//!
80//! # Usage
81//!
82//! ## Setting up your Project
83//!
84//! To use this library, you would put the following lines into your `Cargo.toml` file:
85//!
86//! ```toml
87//! [dependencies]
88//! google-vision1 = "*"
89//! serde = "1"
90//! serde_json = "1"
91//! ```
92//!
93//! ## A complete example
94//!
95//! ```test_harness,no_run
96//! extern crate hyper;
97//! extern crate hyper_rustls;
98//! extern crate google_vision1 as vision1;
99//! use vision1::{Result, Error};
100//! # async fn dox() {
101//! use vision1::{Vision, FieldMask, hyper_rustls, hyper_util, yup_oauth2};
102//!
103//! // Get an ApplicationSecret instance by some means. It contains the `client_id` and
104//! // `client_secret`, among other things.
105//! let secret: yup_oauth2::ApplicationSecret = Default::default();
106//! // Instantiate the authenticator. It will choose a suitable authentication flow for you,
107//! // unless you replace `None` with the desired Flow.
108//! // Provide your own `AuthenticatorDelegate` to adjust the way it operates and get feedback about
109//! // what's going on. You probably want to bring in your own `TokenStorage` to persist tokens and
110//! // retrieve them from storage.
111//! let connector = hyper_rustls::HttpsConnectorBuilder::new()
112//! .with_native_roots()
113//! .unwrap()
114//! .https_only()
115//! .enable_http2()
116//! .build();
117//!
118//! let executor = hyper_util::rt::TokioExecutor::new();
119//! let auth = yup_oauth2::InstalledFlowAuthenticator::with_client(
120//! secret,
121//! yup_oauth2::InstalledFlowReturnMethod::HTTPRedirect,
122//! yup_oauth2::client::CustomHyperClientBuilder::from(
123//! hyper_util::client::legacy::Client::builder(executor).build(connector),
124//! ),
125//! ).build().await.unwrap();
126//!
127//! let client = hyper_util::client::legacy::Client::builder(
128//! hyper_util::rt::TokioExecutor::new()
129//! )
130//! .build(
131//! hyper_rustls::HttpsConnectorBuilder::new()
132//! .with_native_roots()
133//! .unwrap()
134//! .https_or_http()
135//! .enable_http2()
136//! .build()
137//! );
138//! let mut hub = Vision::new(client, auth);
139//! // You can configure optional parameters by calling the respective setters at will, and
140//! // execute the final call using `doit()`.
141//! // Values shown here are possibly random and not representative !
142//! let result = hub.operations().list("name")
143//! .return_partial_success(true)
144//! .page_token("amet.")
145//! .page_size(-20)
146//! .filter("ipsum")
147//! .doit().await;
148//!
149//! match result {
150//! Err(e) => match e {
151//! // The Error enum provides details about what exactly happened.
152//! // You can also just use its `Debug`, `Display` or `Error` traits
153//! Error::HttpError(_)
154//! |Error::Io(_)
155//! |Error::MissingAPIKey
156//! |Error::MissingToken(_)
157//! |Error::Cancelled
158//! |Error::UploadSizeLimitExceeded(_, _)
159//! |Error::Failure(_)
160//! |Error::BadRequest(_)
161//! |Error::FieldClash(_)
162//! |Error::JsonDecodeError(_, _) => println!("{}", e),
163//! },
164//! Ok(res) => println!("Success: {:?}", res),
165//! }
166//! # }
167//! ```
168//! ## Handling Errors
169//!
170//! All errors produced by the system are provided either as [Result](common::Result) enumeration as return value of
171//! the doit() methods, or handed as possibly intermediate results to either the
172//! [Hub Delegate](common::Delegate), or the [Authenticator Delegate](https://docs.rs/yup-oauth2/*/yup_oauth2/trait.AuthenticatorDelegate.html).
173//!
174//! When delegates handle errors or intermediate values, they may have a chance to instruct the system to retry. This
175//! makes the system potentially resilient to all kinds of errors.
176//!
177//! ## Uploads and Downloads
178//! If a method supports downloads, the response body, which is part of the [Result](common::Result), should be
179//! read by you to obtain the media.
180//! If such a method also supports a [Response Result](common::ResponseResult), it will return that by default.
181//! You can see it as meta-data for the actual media. To trigger a media download, you will have to set up the builder by making
182//! this call: `.param("alt", "media")`.
183//!
184//! Methods supporting uploads can do so using up to 2 different protocols:
185//! *simple* and *resumable*. The distinctiveness of each is represented by customized
186//! `doit(...)` methods, which are then named `upload(...)` and `upload_resumable(...)` respectively.
187//!
188//! ## Customization and Callbacks
189//!
190//! You may alter the way an `doit()` method is called by providing a [delegate](common::Delegate) to the
191//! [Method Builder](common::CallBuilder) before making the final `doit()` call.
192//! Respective methods will be called to provide progress information, as well as determine whether the system should
193//! retry on failure.
194//!
195//! The [delegate trait](common::Delegate) is default-implemented, allowing you to customize it with minimal effort.
196//!
197//! ## Optional Parts in Server-Requests
198//!
199//! All structures provided by this library are made to be [encodable](common::RequestValue) and
200//! [decodable](common::ResponseResult) via *json*. Optionals are used to indicate that partial requests are responses
201//! are valid.
202//! Most optionals are are considered [Parts](common::Part) which are identifiable by name, which will be sent to
203//! the server to indicate either the set parts of the request or the desired parts in the response.
204//!
205//! ## Builder Arguments
206//!
207//! Using [method builders](common::CallBuilder), you are able to prepare an action call by repeatedly calling it's methods.
208//! These will always take a single argument, for which the following statements are true.
209//!
210//! * [PODs][wiki-pod] are handed by copy
211//! * strings are passed as `&str`
212//! * [request values](common::RequestValue) are moved
213//!
214//! Arguments will always be copied or cloned into the builder, to make them independent of their original life times.
215//!
216//! [wiki-pod]: http://en.wikipedia.org/wiki/Plain_old_data_structure
217//! [builder-pattern]: http://en.wikipedia.org/wiki/Builder_pattern
218//! [google-go-api]: https://github.com/google/google-api-go-client
219//!
220//! ## Cargo Features
221//!
222//! * `utoipa` - Add support for [utoipa](https://crates.io/crates/utoipa) and derive `utoipa::ToSchema` on all
223//! the types. You'll have to import and register the required types in `#[openapi(schemas(...))]`, otherwise the
224//! generated `openapi` spec would be invalid.
225//!
226//!
227//!
228
229// Unused attributes happen thanks to defined, but unused structures We don't
230// warn about this, as depending on the API, some data structures or facilities
231// are never used. Instead of pre-determining this, we just disable the lint.
232// It's manually tuned to not have any unused imports in fully featured APIs.
233// Same with unused_mut.
234#![allow(unused_imports, unused_mut, dead_code)]
235
236// DO NOT EDIT !
237// This file was generated automatically from 'src/generator/templates/api/lib.rs.mako'
238// DO NOT EDIT !
239
240pub extern crate hyper;
241pub extern crate hyper_rustls;
242pub extern crate hyper_util;
243#[cfg(feature = "yup-oauth2")]
244pub extern crate yup_oauth2;
245
246pub extern crate google_apis_common as common;
247pub use common::{Delegate, Error, FieldMask, Result};
248
249pub mod api;
250pub use api::Vision;