Struct google_blogger3::BlogListByUserCall

pub struct BlogListByUserCall<'a, C, A> where
    C: 'a,
    A: 'a,  { /* fields omitted */ }

Lists blogs by user.

A builder for the listByUser method supported by a blog resource. It is not used directly, but through a BlogMethods instance.

Example

Instantiate a resource method builder

 
// You can configure optional parameters by calling the respective setters at will, and
// execute the final call using `doit()`.
// Values shown here are possibly random and not representative !
let result = hub.blogs().list_by_user("userId")
             .view("eirmod")
             .add_status("elitr")
             .add_role("amet")
             .fetch_user_info(false)
             .doit();

Implementations

impl<'a, C, A> BlogListByUserCall<'a, C, A> where
    C: BorrowMut<Client>,
    A: GetToken, 

pub fn doit(self) -> Result<(Response, BlogList)>

Perform the operation you have build so far.

pub fn user_id(self, new_value: &str) -> BlogListByUserCall<'a, C, A>

Sets the user id path property to the given value.

Even though the property as already been set when instantiating this call, we provide this method for API completeness.

pub fn view(self, new_value: &str) -> BlogListByUserCall<'a, C, A>

Sets the view query property to the given value.

pub fn add_status(self, new_value: &str) -> BlogListByUserCall<'a, C, A>

Default value of status is LIVE.

Append the given value to the status query property. Each appended value will retain its original ordering and be '/'-separated in the URL's parameters.

pub fn add_role(self, new_value: &str) -> BlogListByUserCall<'a, C, A>

Append the given value to the role query property. Each appended value will retain its original ordering and be '/'-separated in the URL's parameters.

pub fn fetch_user_info(self, new_value: bool) -> BlogListByUserCall<'a, C, A>

Sets the fetch user info query property to the given value.

pub fn delegate(
    self,
    new_value: &'a mut dyn Delegate
) -> BlogListByUserCall<'a, C, A>

The delegate implementation is consulted whenever there is an intermediate result, or if something goes wrong while executing the actual API request.

It should be used to handle progress information, and to implement a certain level of resilience.

Sets the delegate property to the given value.

pub fn param<T>(self, name: T, value: T) -> BlogListByUserCall<'a, C, A> where
    T: AsRef<str>, 

Set any additional parameter of the query string used in the request. It should be used to set parameters which are not yet available through their own setters.

Please note that this method must not be used to set any of the known parameters which have their own setter method. If done anyway, the request will fail.

Additional Parameters

• upload_protocol (query-string) - Upload protocol for media (e.g. "raw", "multipart").
• prettyPrint (query-boolean) - Returns response with indentations and line breaks.
• access_token (query-string) - OAuth access token.
• fields (query-string) - Selector specifying which fields to include in a partial response.
• quotaUser (query-string) - Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
• callback (query-string) - JSONP
• oauth_token (query-string) - OAuth 2.0 token for the current user.
• key (query-string) - API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
• uploadType (query-string) - Legacy upload protocol for media (e.g. "media", "multipart").
• alt (query-string) - Data format for response.
• $.xgafv (query-string) - V1 error format.

pub fn add_scope<T, S>(self, scope: T) -> BlogListByUserCall<'a, C, A> where
    T: Into<Option<S>>,
    S: AsRef<str>, 

Identifies the authorization scope for the method you are building.

Use this method to actively specify which scope should be used, instead the default Scope variant Scope::Readonly.

The scope will be added to a set of scopes. This is important as one can maintain access tokens for more than one scope. If None is specified, then all scopes will be removed and no default scope will be used either. In that case, you have to specify your API-key using the key parameter (see the param() function for details).

Usually there is more than one suitable scope to authorize an operation, some of which may encompass more rights than others. For example, for listing resources, a read-only scope will be sufficient, a read-write scope will do as well.

Trait Implementations

impl<'a, C, A> CallBuilder for BlogListByUserCall<'a, C, A>