Re: Moose Troubles

[moritz]

As you can see, what I am attempting to do is provide an interface for the user to pass parameters, then once those parameters are set, the _do_ticket_list function should be called, and return the results of _do_ticket_list results to the ticket_list_response member. Again, everything works the first time around, but every subsequent call does not trigger _do_ticket_list since the ticket_list_response member has already been built

If you want some action to be triggered every time ticket_list_response is accessed, you shouldn't make it an attribute, but a method right away.

[three18ti]

Hello,
Thank you for the reply.

I guess my confusion is, ticket_list_response is an object that delegates methods, changing ticket_list_response to a method then won't allow me to call object methods later.

For instance, I want to initialize ticket_list_response attribute, then call count_tickets on the ticket_list_response object.

#!/usr/bin/perl

use Kayako3::Staff;

# this initializes  Kayako3::Staff object,
# performs the login,
# parses the login response and stores the user session ID,
# then initializes the info_response object which provides 
# all the info for id lookups later on
my $help_desk = Kayako3::Staff->new({
    username => 'bob',
    password => 'my_pass',
    api_url => 'http://example.com/staffapi?',
});

# since the API requires integer ids, 
# I perform a lookup in separate steps for clarity
# usually, I'll perform this all in one step:
# $help_desk->get_ticket_list( 
#    $help_desk->get_department_id("Support"), 
#    $help_desk->get_ticket_status_id("New") 
# );

my $department_id = $help_desk->get_department_id("Support");
my $ticket_status_id = $help_desk->get_ticket_status_id("New");

$hd->get_ticket_list($department_id, $ticket_status_id)

# once the ticket is loaded:
print "Ticket count in " 
    . $help_desk->ticket_list_response->department 
    . ", for tickets with status " 
    . $help_desk->ticket_list_response->status 
    . ": " 
    . $help_desk->get_ticket_count . "\n";

# sample output:  
# Ticket count in Support, for tickets with status New: 10

# then later on, I want to do the same thing 
# for a different department:
my $department_id = $help_desk->get_department_id("Sales");
my $ticket_status_id 
    = $help_desk->get_ticket_status_id("In progress");

$hd->get_ticket_list($department_id, $ticket_status_id)

#Then I want to print the ticket count again, 
# for the new department, 
# but performing $help_desk->get_ticket_count 
# returns the same results above
print "Ticket count in " 
    . $help_desk->ticket_list_response->department 
    . ", for tickets with status " 
    . $help_desk->ticket_list_response->status 
    . ": " 
    . $help_desk->get_ticket_count . "\n";

# sample output:  
# Ticket count in Support, for tickets with status New: 10
# desired ouutput:  
# Ticket count in Sales, for tickets with status In Progress: 15

Usually, I wouldn't call $help_desk->_ticket_list_response->department directly, however, it is important to help illustrate my problem.

I don't want to call ticket_list_response directly because it only provides a place holder to store the Kayako3::Staff:Response::TicketList object.

[CountZero]

When you want the ticket count for another department and/or another status shouldn't you start with a new object, rather than with an already existing object? Your _do_ticket_list method will only be called at the object's initialization, so changing the department id or the ticket status will go unnoticed and the ticket list is never refreshed.

Reader beware: my Moose skills may be a bit rusty and the finer issues of builders and triggers may have escaped me.

Update: Question: where does your $hd object come from? I never see you initialize it. Or is it perhaps a typo and did you mean $help_desk?

[moritz]

I guess my confusion is, ticket_list_response is an object that delegates methods, changing ticket_list_response to a method then won't allow me to call object methods later.

Then store the object that is now stored in ticket_list_response somewhere else (for example in a private attribute), and make ticket_list_response a method that does whatever you want it to do whenever it is called.