Struct PostTextRequest

pub struct PostTextRequest {
    pub active_contexts: Option<Vec<ActiveContext>>,
    pub bot_alias: String,
    pub bot_name: String,
    pub input_text: String,
    pub request_attributes: Option<HashMap<String, String>>,
    pub session_attributes: Option<HashMap<String, String>>,
    pub user_id: String,
}

Fields

active_contexts: Option<Vec<ActiveContext>>

A list of contexts active for the request. A context can be activated when a previous intent is fulfilled, or by including the context in the request,

If you don't specify a list of contexts, Amazon Lex will use the current list of contexts for the session. If you specify an empty list, all contexts for the session are cleared.

bot_alias: String

The alias of the Amazon Lex bot.

bot_name: String

The name of the Amazon Lex bot.

input_text: String

The text that the user entered (Amazon Lex interprets this text).

request_attributes: Option<HashMap<String, String>>

Request-specific information passed between Amazon Lex and a client application.

The namespace x-amz-lex: is reserved for special attributes. Don't create any request attributes with the prefix x-amz-lex:.

For more information, see Setting Request Attributes.

session_attributes: Option<HashMap<String, String>>

Application-specific information passed between Amazon Lex and a client application.

For more information, see Setting Session Attributes.

user_id: String

The ID of the client application user. Amazon Lex uses this to identify a user's conversation with your bot. At runtime, each request must contain the userID field.

To decide the user ID to use for your application, consider the following factors.

• The userID field must not contain any personally identifiable information of the user, for example, name, personal identification numbers, or other end user personal information.

• If you want a user to start a conversation on one device and continue on another device, use a user-specific identifier.

• If you want the same user to be able to have two independent conversations on two different devices, choose a device-specific identifier.

• A user can't have two independent conversations with two different versions of the same bot. For example, a user can't have a conversation with the PROD and BETA versions of the same bot. If you anticipate that a user will need to have conversation with two different versions, for example, while testing, include the bot alias in the user ID to separate the two conversations.

Trait Implementations

impl Clone for PostTextRequest

fn clone(&self) -> PostTextRequest

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for PostTextRequest

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

Formats the value using the given formatter.

impl Default for PostTextRequest

fn default() -> PostTextRequest

Returns the “default value” for a type.

impl PartialEq for PostTextRequest

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

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for PostTextRequest