Skip Menu |

This queue is for tickets about the Net-Google-FederatedLogin CPAN distribution.

Report information
The Basics
Id: 66332
Status: resolved
Priority: 0/
Queue: Net-Google-FederatedLogin

People
Owner: Nobody in particular
Requestors: erik.gimbert [...] groupsquad.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 0.7.0



Subject: use FederatedLogin with Catalyst
Date: Wed, 2 Mar 2011 18:16:29 +0100
To: bug-Net-Google-FederatedLogin [...] rt.cpan.org
From: Erik Gimbert <erik.gimbert [...] groupsquad.com>
I encountered a problem trying to use Net-Google-FederatedLogin-0.5.3 with Catalyst. The attribute, of the method new(), cgi want a CGI object, I is not with Catalyst. So I had to replace it with an object Catalyst:: Request, which also has a method param(). It would be more convenient to directly pass a HashRef which contain the parameters.
On Wed Mar 02 12:16:40 2011, erik.gimbert@groupsquad.com wrote: Show quoted text
> I encountered a problem trying to use Net-Google-FederatedLogin-0.5.3 > with Catalyst. The attribute, of the method new(), cgi want a CGI object, I > is not with Catalyst. So I had to replace it with an object Catalyst:: > Request, which also has a method param(). > > It would be more convenient to directly pass a HashRef which contain the > parameters.
OK, good point. I think I'll keep the cgi attribute, but widen that up to be happy with any object that behaves the same way as CGI where param() is concerned, and add a cgi_params (or something) attribute that can be used instead for the hashref. Obviously only one of cgi or cgi_params would be required.
Subject: Re: [rt.cpan.org #66332] use FederatedLogin with Catalyst
Date: Wed, 9 Mar 2011 09:56:11 +0100
To: Glenn Fowler via RT <bug-Net-Google-FederatedLogin [...] rt.cpan.org>
From: erik.gimbert [...] groupsquad.com
On Wed, Mar 09, 2011 at 02:25:07AM -0500, Glenn Fowler via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=66332 > > > OK, good point. > > I think I'll keep the cgi attribute, but widen that up to be happy with any object that behaves the > same way as CGI where param() is concerned, and add a cgi_params (or something) attribute > that can be used instead for the hashref. Obviously only one of cgi or cgi_params would be > required.
Ok, thank
Fixed in 0.7.0