mirror of
https://github.com/OMGeeky/google-apis-rs.git
synced 2026-02-23 15:49:49 +01:00
Regen all remaining APIs with preproc - more changes than anticipated
This commit is contained in:
@@ -1240,7 +1240,8 @@ pub struct Location {
|
||||
pub display_name: Option<String>,
|
||||
/// Cross-service attributes for the location. For example
|
||||
///
|
||||
/// {"cloud.googleapis.com/region": "us-east1"}
|
||||
/// ````text
|
||||
/// {"cloud.googleapis.com/region": "us-east1"}````
|
||||
pub labels: Option<HashMap<String, String>>,
|
||||
/// The canonical id for this location. For example: `"us-east1"`.
|
||||
#[serde(rename="locationId")]
|
||||
@@ -1391,9 +1392,11 @@ impl ResponseResult for GoogleFirestoreAdminV1ListIndexesResponse {}
|
||||
/// empty messages in your APIs. A typical example is to use it as the request
|
||||
/// or the response type of an API method. For instance:
|
||||
///
|
||||
/// service Foo {
|
||||
/// rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty);
|
||||
/// }
|
||||
/// ````text
|
||||
/// service Foo {
|
||||
/// rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty);
|
||||
/// }
|
||||
/// ````
|
||||
///
|
||||
/// The JSON representation for `Empty` is empty JSON object `{}`.
|
||||
///
|
||||
@@ -1407,7 +1410,6 @@ impl ResponseResult for GoogleFirestoreAdminV1ListIndexesResponse {}
|
||||
/// * [databases operations delete projects](struct.ProjectDatabaseOperationDeleteCall.html) (response)
|
||||
/// * [databases collection groups indexes delete projects](struct.ProjectDatabaseCollectionGroupIndexeDeleteCall.html) (response)
|
||||
/// * [databases documents rollback projects](struct.ProjectDatabaseDocumentRollbackCall.html) (response)
|
||||
///
|
||||
#[derive(Default, Clone, Debug, Serialize, Deserialize)]
|
||||
pub struct Empty { _never_set: Option<bool> }
|
||||
|
||||
@@ -1493,8 +1495,8 @@ impl RequestValue for BatchGetDocumentsRequest {}
|
||||
/// different programming environments, including REST APIs and RPC APIs. It is
|
||||
/// used by [gRPC](https://github.com/grpc). The error model is designed to be:
|
||||
///
|
||||
/// - Simple to use and understand for most users
|
||||
/// - Flexible enough to meet unexpected needs
|
||||
/// * Simple to use and understand for most users
|
||||
/// * Flexible enough to meet unexpected needs
|
||||
///
|
||||
/// # Overview
|
||||
///
|
||||
@@ -1524,26 +1526,25 @@ impl RequestValue for BatchGetDocumentsRequest {}
|
||||
///
|
||||
/// Example uses of this error model include:
|
||||
///
|
||||
/// - Partial errors. If a service needs to return partial errors to the client,
|
||||
/// it may embed the `Status` in the normal response to indicate the partial
|
||||
/// errors.
|
||||
/// * Partial errors. If a service needs to return partial errors to the client,
|
||||
/// it may embed the `Status` in the normal response to indicate the partial
|
||||
/// errors.
|
||||
///
|
||||
/// - Workflow errors. A typical workflow has multiple steps. Each step may
|
||||
/// have a `Status` message for error reporting.
|
||||
/// * Workflow errors. A typical workflow has multiple steps. Each step may
|
||||
/// have a `Status` message for error reporting.
|
||||
///
|
||||
/// - Batch operations. If a client uses batch request and batch response, the
|
||||
/// `Status` message should be used directly inside batch response, one for
|
||||
/// each error sub-response.
|
||||
/// * Batch operations. If a client uses batch request and batch response, the
|
||||
/// `Status` message should be used directly inside batch response, one for
|
||||
/// each error sub-response.
|
||||
///
|
||||
/// - Asynchronous operations. If an API call embeds asynchronous operation
|
||||
/// results in its response, the status of those operations should be
|
||||
/// represented directly using the `Status` message.
|
||||
/// * Asynchronous operations. If an API call embeds asynchronous operation
|
||||
/// results in its response, the status of those operations should be
|
||||
/// represented directly using the `Status` message.
|
||||
///
|
||||
/// - Logging. If some API errors are stored in logs, the message `Status` could
|
||||
/// be used directly after any stripping needed for security/privacy reasons.
|
||||
/// * Logging. If some API errors are stored in logs, the message `Status` could
|
||||
/// be used directly after any stripping needed for security/privacy reasons.
|
||||
///
|
||||
/// This type is not used in any activity, and only used as *part* of another schema.
|
||||
///
|
||||
#[derive(Default, Clone, Debug, Serialize, Deserialize)]
|
||||
pub struct Status {
|
||||
/// A developer-facing error message, which should be in English. Any
|
||||
|
||||
Reference in New Issue
Block a user