blib/lib/Paws/LexModels/FulfillmentActivity.pm untested

filter: Statementstmt 0.0% 0 / 7 Branchbran n/a Conditioncond n/a MC/DCmcdc n/a Subroutinesub 0.0% 0 / 1 Podpod n/a totaltotal 0.0% 0 / 8 CC 1 SCAR 6.9
CC
1
Cov
0%
BEGIN
2.0
CRAP 2.0
1 # Generated by default/object.tt
2 package Paws::LexModels::FulfillmentActivity;
3 use Moose;
4 has CodeHook => (is => 'ro', isa => 'Paws::LexModels::CodeHook', request_name => 'codeHook', traits => ['NameInRequest']);
5 has Type => (is => 'ro', isa => 'Str', request_name => 'type', traits => ['NameInRequest'], required => 1);
6  
7 1;
8  
9 ### main pod documentation begin ###
10  
11 =head1 NAME
12  
13 Paws::LexModels::FulfillmentActivity
14  
15 =head1 USAGE
16  
17 This class represents one of two things:
18  
19 =head3 Arguments in a call to a service
20  
21 Use the attributes of this class as arguments to methods. You shouldn't make instances of this class.
22 Each attribute should be used as a named argument in the calls that expect this type of object.
23  
24 As an example, if Att1 is expected to be a Paws::LexModels::FulfillmentActivity object:
25  
26 $service_obj->Method(Att1 => { CodeHook => $value, ..., Type => $value });
27  
28 =head3 Results returned from an API call
29  
30 Use accessors for each attribute. If Att1 is expected to be an Paws::LexModels::FulfillmentActivity object:
31  
32 $result = $service_obj->Method(...);
33 $result->Att1->CodeHook
34  
35 =head1 DESCRIPTION
36  
37 Describes how the intent is fulfilled after the user provides all of
38 the information required for the intent. You can provide a Lambda
39 function to process the intent, or you can return the intent
40 information to the client application. We recommend that you use a
41 Lambda function so that the relevant logic lives in the Cloud and limit
42 the client-side code primarily to presentation. If you need to update
43 the logic, you only update the Lambda function; you don't need to
44 upgrade your client application.
45  
46 Consider the following examples:
47  
48 =over
49  
50 =item *
51  
52 In a pizza ordering application, after the user provides all of the
53 information for placing an order, you use a Lambda function to place an
54 order with a pizzeria.
55  
56 =item *
57  
58 In a gaming application, when a user says "pick up a rock," this
59 information must go back to the client application so that it can
60 perform the operation and update the graphics. In this case, you want
61 Amazon Lex to return the intent data to the client.
62  
63 =back
64  
65  
66 =head1 ATTRIBUTES
67  
68  
69 =head2 CodeHook => L<Paws::LexModels::CodeHook>
70  
71 A description of the Lambda function that is run to fulfill the intent.
72  
73  
74 =head2 B<REQUIRED> Type => Str
75  
76 How the intent should be fulfilled, either by running a Lambda function
77 or by returning the slot data to the client application.
78  
79  
80  
81 =head1 SEE ALSO
82  
83 This class forms part of L<Paws>, describing an object used in L<Paws::LexModels>
84  
85 =head1 BUGS and CONTRIBUTIONS
86  
87 The source code is located here: L<https://github.com/pplu/aws-sdk-perl>
88  
89 Please report bugs to: L<https://github.com/pplu/aws-sdk-perl/issues>
90  
91 =cut
92