make regen-apis

This commit is contained in:
OMGeeky
2023-10-21 02:11:31 +02:00
parent 557df5b43f
commit bcacb792b1
964 changed files with 11866 additions and 11866 deletions

View File

@@ -23,7 +23,7 @@ use crate::{client, client::GetToken, client::serde_with};
/// Identifies the an OAuth2 authorization scope.
/// A scope is needed when requesting an
/// [authorization token](https://developers.google.com/youtube/v3/guides/authentication).
#[derive(PartialEq, Eq, Hash)]
#[derive(PartialEq, Eq, Hash, Debug)]
pub enum Scope {
/// See, edit, configure, and delete your Google Cloud data and see the email address for your Google Account.
CloudPlatform,
@@ -65,12 +65,12 @@ impl Default for Scope {
/// use std::default::Default;
/// use datalabeling1_beta1::{DataLabeling, oauth2, hyper, hyper_rustls, chrono, FieldMask};
///
/// // Get an ApplicationSecret instance by some means. It contains the `client_id` and
/// // Get an ApplicationSecret instance by some means. It contains the `client_id` and
/// // `client_secret`, among other things.
/// let secret: oauth2::ApplicationSecret = Default::default();
/// // Instantiate the authenticator. It will choose a suitable authentication flow for you,
/// // Instantiate the authenticator. It will choose a suitable authentication flow for you,
/// // unless you replace `None` with the desired Flow.
/// // Provide your own `AuthenticatorDelegate` to adjust the way it operates and get feedback about
/// // Provide your own `AuthenticatorDelegate` to adjust the way it operates and get feedback about
/// // what's going on. You probably want to bring in your own `TokenStorage` to persist tokens and
/// // retrieve them from storage.
/// let auth = oauth2::InstalledFlowAuthenticator::builder(

View File

@@ -9,7 +9,7 @@
//! The original source code is [on github](https://github.com/Byron/google-apis-rs/tree/main/gen/datalabeling1_beta1).
//! # Features
//!
//! Handle the following *Resources* with ease from the central [hub](DataLabeling) ...
//! Handle the following *Resources* with ease from the central [hub](DataLabeling) ...
//!
//! * projects
//! * [*annotation spec sets create*](api::ProjectAnnotationSpecSetCreateCall), [*annotation spec sets delete*](api::ProjectAnnotationSpecSetDeleteCall), [*annotation spec sets get*](api::ProjectAnnotationSpecSetGetCall), [*annotation spec sets list*](api::ProjectAnnotationSpecSetListCall), [*datasets annotated datasets data items get*](api::ProjectDatasetAnnotatedDatasetDataItemGetCall), [*datasets annotated datasets data items list*](api::ProjectDatasetAnnotatedDatasetDataItemListCall), [*datasets annotated datasets delete*](api::ProjectDatasetAnnotatedDatasetDeleteCall), [*datasets annotated datasets examples get*](api::ProjectDatasetAnnotatedDatasetExampleGetCall), [*datasets annotated datasets examples list*](api::ProjectDatasetAnnotatedDatasetExampleListCall), [*datasets annotated datasets feedback threads delete*](api::ProjectDatasetAnnotatedDatasetFeedbackThreadDeleteCall), [*datasets annotated datasets feedback threads feedback messages create*](api::ProjectDatasetAnnotatedDatasetFeedbackThreadFeedbackMessageCreateCall), [*datasets annotated datasets feedback threads feedback messages delete*](api::ProjectDatasetAnnotatedDatasetFeedbackThreadFeedbackMessageDeleteCall), [*datasets annotated datasets feedback threads feedback messages get*](api::ProjectDatasetAnnotatedDatasetFeedbackThreadFeedbackMessageGetCall), [*datasets annotated datasets feedback threads feedback messages list*](api::ProjectDatasetAnnotatedDatasetFeedbackThreadFeedbackMessageListCall), [*datasets annotated datasets feedback threads get*](api::ProjectDatasetAnnotatedDatasetFeedbackThreadGetCall), [*datasets annotated datasets feedback threads list*](api::ProjectDatasetAnnotatedDatasetFeedbackThreadListCall), [*datasets annotated datasets get*](api::ProjectDatasetAnnotatedDatasetGetCall), [*datasets annotated datasets list*](api::ProjectDatasetAnnotatedDatasetListCall), [*datasets create*](api::ProjectDatasetCreateCall), [*datasets data items get*](api::ProjectDatasetDataItemGetCall), [*datasets data items list*](api::ProjectDatasetDataItemListCall), [*datasets delete*](api::ProjectDatasetDeleteCall), [*datasets evaluations example comparisons search*](api::ProjectDatasetEvaluationExampleComparisonSearchCall), [*datasets evaluations get*](api::ProjectDatasetEvaluationGetCall), [*datasets export data*](api::ProjectDatasetExportDataCall), [*datasets get*](api::ProjectDatasetGetCall), [*datasets image label*](api::ProjectDatasetImageLabelCall), [*datasets import data*](api::ProjectDatasetImportDataCall), [*datasets list*](api::ProjectDatasetListCall), [*datasets text label*](api::ProjectDatasetTextLabelCall), [*datasets video label*](api::ProjectDatasetVideoLabelCall), [*evaluation jobs create*](api::ProjectEvaluationJobCreateCall), [*evaluation jobs delete*](api::ProjectEvaluationJobDeleteCall), [*evaluation jobs get*](api::ProjectEvaluationJobGetCall), [*evaluation jobs list*](api::ProjectEvaluationJobListCall), [*evaluation jobs patch*](api::ProjectEvaluationJobPatchCall), [*evaluation jobs pause*](api::ProjectEvaluationJobPauseCall), [*evaluation jobs resume*](api::ProjectEvaluationJobResumeCall), [*evaluations search*](api::ProjectEvaluationSearchCall), [*instructions create*](api::ProjectInstructionCreateCall), [*instructions delete*](api::ProjectInstructionDeleteCall), [*instructions get*](api::ProjectInstructionGetCall), [*instructions list*](api::ProjectInstructionListCall), [*operations cancel*](api::ProjectOperationCancelCall), [*operations delete*](api::ProjectOperationDeleteCall), [*operations get*](api::ProjectOperationGetCall) and [*operations list*](api::ProjectOperationListCall)
@@ -60,8 +60,8 @@
//! let r = hub.projects().operations_delete(...).doit().await
//! ```
//!
//! The `resource()` and `activity(...)` calls create [builders][builder-pattern]. The second one dealing with `Activities`
//! supports various methods to configure the impending operation (not shown here). It is made such that all required arguments have to be
//! The `resource()` and `activity(...)` calls create [builders][builder-pattern]. The second one dealing with `Activities`
//! supports various methods to configure the impending operation (not shown here). It is made such that all required arguments have to be
//! specified right away (i.e. `(...)`), whereas all optional ones can be [build up][builder-pattern] as desired.
//! The `doit()` method performs the actual communication with the server and returns the respective result.
//!
@@ -90,12 +90,12 @@
//! use std::default::Default;
//! use datalabeling1_beta1::{DataLabeling, oauth2, hyper, hyper_rustls, chrono, FieldMask};
//!
//! // Get an ApplicationSecret instance by some means. It contains the `client_id` and
//! // Get an ApplicationSecret instance by some means. It contains the `client_id` and
//! // `client_secret`, among other things.
//! let secret: oauth2::ApplicationSecret = Default::default();
//! // Instantiate the authenticator. It will choose a suitable authentication flow for you,
//! // Instantiate the authenticator. It will choose a suitable authentication flow for you,
//! // unless you replace `None` with the desired Flow.
//! // Provide your own `AuthenticatorDelegate` to adjust the way it operates and get feedback about
//! // Provide your own `AuthenticatorDelegate` to adjust the way it operates and get feedback about
//! // what's going on. You probably want to bring in your own `TokenStorage` to persist tokens and
//! // retrieve them from storage.
//! let auth = oauth2::InstalledFlowAuthenticator::builder(
@@ -136,10 +136,10 @@
//! ## Handling Errors
//!
//! All errors produced by the system are provided either as [Result](client::Result) enumeration as return value of
//! the doit() methods, or handed as possibly intermediate results to either the
//! the doit() methods, or handed as possibly intermediate results to either the
//! [Hub Delegate](client::Delegate), or the [Authenticator Delegate](https://docs.rs/yup-oauth2/*/yup_oauth2/trait.AuthenticatorDelegate.html).
//!
//! When delegates handle errors or intermediate values, they may have a chance to instruct the system to retry. This
//! When delegates handle errors or intermediate values, they may have a chance to instruct the system to retry. This
//! makes the system potentially resilient to all kinds of errors.
//!
//! ## Uploads and Downloads
@@ -149,25 +149,25 @@
//! 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
//! this call: `.param("alt", "media")`.
//!
//! Methods supporting uploads can do so using up to 2 different protocols:
//! *simple* and *resumable*. The distinctiveness of each is represented by customized
//! Methods supporting uploads can do so using up to 2 different protocols:
//! *simple* and *resumable*. The distinctiveness of each is represented by customized
//! `doit(...)` methods, which are then named `upload(...)` and `upload_resumable(...)` respectively.
//!
//! ## Customization and Callbacks
//!
//! You may alter the way an `doit()` method is called by providing a [delegate](client::Delegate) to the
//! [Method Builder](client::CallBuilder) before making the final `doit()` call.
//! Respective methods will be called to provide progress information, as well as determine whether the system should
//! You may alter the way an `doit()` method is called by providing a [delegate](client::Delegate) to the
//! [Method Builder](client::CallBuilder) before making the final `doit()` call.
//! Respective methods will be called to provide progress information, as well as determine whether the system should
//! retry on failure.
//!
//! The [delegate trait](client::Delegate) is default-implemented, allowing you to customize it with minimal effort.
//!
//! ## Optional Parts in Server-Requests
//!
//! All structures provided by this library are made to be [encodable](client::RequestValue) and
//! [decodable](client::ResponseResult) via *json*. Optionals are used to indicate that partial requests are responses
//! All structures provided by this library are made to be [encodable](client::RequestValue) and
//! [decodable](client::ResponseResult) via *json*. Optionals are used to indicate that partial requests are responses
//! are valid.
//! Most optionals are are considered [Parts](client::Part) which are identifiable by name, which will be sent to
//! Most optionals are are considered [Parts](client::Part) which are identifiable by name, which will be sent to
//! the server to indicate either the set parts of the request or the desired parts in the response.
//!
//! ## Builder Arguments