Skip Menu |

This queue is for tickets about the Test-WWW-Mechanize-Mojo CPAN distribution.

Report information
The Basics
Id: 88321
Status: open
Priority: 0/
Queue: Test-WWW-Mechanize-Mojo

People
Owner: Nobody in particular
Requestors: dsteinbrunner [...] pobox.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: v0.0.13
Fixed in: (no value)



Subject: Docs appear to not be completely converted to Mojo
In the CONSTRUCTOR section the code references Test::WWW::Mechanize::Catalyst twice rather than Test::WWW::Mechanize::Mojo and says: Note that we need to pass the name of the Catalyst application to the "use" But the follow code shows something else going on. Above that section on the code there is this: $mmech->{catalyst_debug} = 1; First $mmech should be $mech. Secondly the use of catalyst would seem to need to be mojo. On the surface it seems like this might be an issue with just the POD but the code makes use of catalyst_debug. catalyst_debug
Hi, On Sun Sep 01 14:40:36 2013, dsteinbrunner@pobox.com wrote: Show quoted text
> In the CONSTRUCTOR section the code references > Test::WWW::Mechanize::Catalyst twice rather than > Test::WWW::Mechanize::Mojo and says: > > Note that we need to pass the name of the Catalyst application to the > "use" > > But the follow code shows something else going on. > > Above that section on the code there is this: > > $mmech->{catalyst_debug} = 1; > > First $mmech should be $mech. Secondly the use of catalyst would seem > to need to be mojo. On the surface it seems like this might be an > issue with just the POD but the code makes use of catalyst_debug. > > catalyst_debug
thanks for the report and sorry it took me so long to get back to you. I've originally written this module for a Mojo project I did and got paid for, and since then I haven't been using Mojo a lot. As a result, the module is in deep maintenance mode. If anybody is interested in fixing this issue, they can send me a pull request at https://bitbucket.org/shlomif/perl-test-www-mechanize-mojo . Otherwise, I'm probably not going to fix it soon because this module is not a high priority for me. Regards, -- Shlomi Fish