Struct InAppTemplateResponse 

#[non_exhaustive]
pub struct InAppTemplateResponse {
    pub arn: Option<String>,
    pub content: Option<Vec<InAppMessageContent>>,
    pub creation_date: Option<String>,
    pub custom_config: Option<HashMap<String, String>>,
    pub last_modified_date: Option<String>,
    pub layout: Option<Layout>,
    pub tags: Option<HashMap<String, String>>,
    pub template_description: Option<String>,
    pub template_name: Option<String>,
    pub template_type: Option<TemplateType>,
    pub version: Option<String>,
}

In-App Template Response.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

arn: Option<String>

The resource arn of the template.

content: Option<Vec<InAppMessageContent>>

The content of the message, can include up to 5 modals. Each modal must contain a message, a header, and background color. ImageUrl and buttons are optional.

creation_date: Option<String>

The creation date of the template.

custom_config: Option<HashMap<String, String>>

Custom config to be sent to client.

last_modified_date: Option<String>

The last modified date of the template.

layout: Option<Layout>

The layout of the message.

tags: Option<HashMap<String, String>>

A string-to-string map of key-value pairs that defines the tags to associate with the message template. Each tag consists of a required tag key and an associated tag value.

template_description: Option<String>

The description of the template.

template_name: Option<String>

The name of the template.

template_type: Option<TemplateType>

The type of the template.

version: Option<String>

The version id of the template.

Implementations

impl InAppTemplateResponse

pub fn arn(&self) -> Option<&str>

The resource arn of the template.

pub fn content(&self) -> &[InAppMessageContent]

The content of the message, can include up to 5 modals. Each modal must contain a message, a header, and background color. ImageUrl and buttons are optional.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .content.is_none().

pub fn creation_date(&self) -> Option<&str>

The creation date of the template.

pub fn custom_config(&self) -> Option<&HashMap<String, String>>

Custom config to be sent to client.

pub fn last_modified_date(&self) -> Option<&str>

The last modified date of the template.

pub fn layout(&self) -> Option<&Layout>

The layout of the message.

pub fn tags(&self) -> Option<&HashMap<String, String>>

A string-to-string map of key-value pairs that defines the tags to associate with the message template. Each tag consists of a required tag key and an associated tag value.

pub fn template_description(&self) -> Option<&str>

The description of the template.

pub fn template_name(&self) -> Option<&str>

The name of the template.

pub fn template_type(&self) -> Option<&TemplateType>

The type of the template.

pub fn version(&self) -> Option<&str>

The version id of the template.

impl InAppTemplateResponse

pub fn builder() -> InAppTemplateResponseBuilder

Creates a new builder-style object to manufacture InAppTemplateResponse.

Trait Implementations

impl Clone for InAppTemplateResponse

fn clone(&self) -> InAppTemplateResponse

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for InAppTemplateResponse

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq for InAppTemplateResponse

fn eq(&self, other: &InAppTemplateResponse) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for InAppTemplateResponse