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