Struct AttachmentInput 

#[non_exhaustive]
pub struct AttachmentInput {
    pub data: Option<Blob>,
    pub name: Option<String>,
    pub copy_from: Option<CopyFromSource>,
}

This is either a file directly uploaded into a web experience chat or a reference to an existing attachment that is part of a web experience chat.

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.

data: Option<Blob>

The contents of the attachment.

name: Option<String>

The filename of the attachment.

copy_from: Option<CopyFromSource>

A reference to an existing attachment.

Implementations

impl AttachmentInput

pub fn data(&self) -> Option<&Blob>

The contents of the attachment.

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

The filename of the attachment.

pub fn copy_from(&self) -> Option<&CopyFromSource>

A reference to an existing attachment.

impl AttachmentInput

pub fn builder() -> AttachmentInputBuilder

Creates a new builder-style object to manufacture AttachmentInput.

Trait Implementations

impl Clone for AttachmentInput

fn clone(&self) -> AttachmentInput

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for AttachmentInput

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

Formats the value using the given formatter.

impl PartialEq for AttachmentInput

fn eq(&self, other: &AttachmentInput) -> 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 AttachmentInput