Struct google_docs1::api::DocumentMethods

source ·

pub struct DocumentMethods<'a, S>where
    S: 'a,
{ /* private fields */ }

Expand description

A builder providing access to all methods supported on document resources. It is not used directly, but through the Docs hub.

§Example

Instantiate a resource builder

extern crate hyper;
extern crate hyper_rustls;
extern crate google_docs1 as docs1;
 
use std::default::Default;
use docs1::{Docs, oauth2, hyper, hyper_rustls, chrono, FieldMask};
 
let secret: oauth2::ApplicationSecret = Default::default();
let auth = oauth2::InstalledFlowAuthenticator::builder(
        secret,
        oauth2::InstalledFlowReturnMethod::HTTPRedirect,
    ).build().await.unwrap();
let mut hub = Docs::new(hyper::Client::builder().build(hyper_rustls::HttpsConnectorBuilder::new().with_native_roots().https_or_http().enable_http1().build()), auth);
// Usually you wouldn't bind this to a variable, but keep calling *CallBuilders*
// like `batch_update(...)`, `create(...)` and `get(...)`
// to build up your call.
let rb = hub.documents();

Implementations§

source §

impl<'a, S> DocumentMethods<'a, S>

source

pub fn batch_update( &self, request: BatchUpdateDocumentRequest, document_id: &str ) -> DocumentBatchUpdateCall<'a, S>

Create a builder to help you perform the following task:

Applies one or more updates to the document. Each request is validated before being applied. If any request is not valid, then the entire request will fail and nothing will be applied. Some requests have replies to give you some information about how they are applied. Other requests do not need to return information; these each return an empty reply. The order of replies matches that of the requests. For example, suppose you call batchUpdate with four updates, and only the third one returns information. The response would have two empty replies, the reply to the third request, and another empty reply, in that order. Because other users may be editing the document, the document might not exactly reflect your changes: your changes may be altered with respect to collaborator changes. If there are no collaborators, the document should reflect your changes. In any case, the updates in your request are guaranteed to be applied together atomically.

§Arguments

request - No description provided.
documentId - The ID of the document to update.

source

pub fn create(&self, request: Document) -> DocumentCreateCall<'a, S>

Create a builder to help you perform the following task:

Creates a blank document using the title given in the request. Other fields in the request, including any provided content, are ignored. Returns the created document.