September 2015 - dancer-users - lists.preshweb.co.uk

Reaching a route defined at another .pm file
by Kadir Beyazlı 14 Sep '15

14 Sep '15

Hi All, At my project all routes are defined at same file : myproject.pm as follow: get /product { } get /store { } get /user { } Then I decided to put each logical item into separate file as follow, for example I created Product.pm for product operations. #Product.pm package Product; use Dancer2; get /product { } At file myproject.pm I added package Product as follow and removed route from this file myproject.pm package myproject; use Dancer2; use Dancer2::Plugin::Database; use Product; But it can not find get /product route which was working when it was at myproject.pm How can I do it? -- Kadir Beyazlı GSM : +90 535 821 50 00

2 4

config.yml YAML warning
by Kadir Beyazlı 13 Sep '15

13 Sep '15

Hi All, I decided to use YAML session and added following codes to config.yml reading article of which link is below: https://metacpan.org/pod/Dancer2::Manual#SESSIONS 1 session: YAML 2 engines: 3 session: 4 YAML: 5 session_dir: /tmp/dancer-sessions It works but at my .pm file, following definition is underlined use Dancer2; and when I mouse over above definition I see following warning : YAML Warning: Duplicate map key found. Ignoring ..... I also attached full warning message screenshot I removed 1st line above but it warning still exists. -- Kadir Beyazlı GSM : +90 535 821 50 00

1 0

Disabling main layout
by Kadir Beyazlı 13 Sep '15

13 Sep '15

Hi All, I think I saw solution at mails but could not find at my search so I have to ask here. I set main layout. But I don't want main layout to be loaded at route /login. Is it possible disabling main layout at route /login although I am using template in it? *get '/login' => sub { template 'login', { path => param('requested_path') };};* -- *Kadir Beyazlı* *GSM : +90 535 821 50 00*

5 10

Re: [dancer-users] dancer online resources
by Rick Leir 12 Sep '15

12 Sep '15

On Fri, Sep 11, 2015 at 7:00 AM, Yanick wrote: > > On 2015-09-10 02:28 AM, Stefan Hornburg (Racke) wrote: >> as far as I know there is no book about Dancer yet. >> >> There is a lot of other resources online though. > > Indeed. There are, amongst others things, the various Advent Calendars: > http://advent.perldancer.org/2014 As well as the core documentation > itself, of course. > > `/. > Lots of online intros! Advent, and: http://perlmaven.com/dancer https://metacpan.org/pod/Dancer::Introduction http://search.cpan.org/~sukria/Dancer2-0.01/lib/Dancer2/Cookbook.pod http://webcache.googleusercontent.com/search?q=cache:4aPi66j_thEJ:www.aibis… cheers -- Rick

3 2

Setting Session Engine
by Richard Reina 11 Sep '15

11 Sep '15

I am trying to get Deferred to work but keep getting: Error 500: core - Must specify session engine in settings prior to using 'session' keyword at /home/richard/perl5/lib/perl5/Dancer/Plugin/Deferred.pm line 26. Powered by Dancer2 <http://perldancer.org/> 0.161000 I have used the command: set session => 'YAML'; to set the session. I have also tried session: "YAML" in my config file. Is there something else I must do?

3 3

dancer book?
by Ken Peng 11 Sep '15

11 Sep '15

Hi, I have wrote some code with Perl and Dancer, they work fine. Now I want to take a deep look at this framework. I searched but have no luck for finding a special book about Dancer. Have you known anyone? Thanks. -- B. Regards, Ken Peng - ken(a)cloud-china.org

8 10

interpolate a Javascript variable as to assign it's value to a TT variable
by Nikos Vaggalis 08 Sep '15

08 Sep '15

More educational value out of this question than a practical one Is it possible to interpolate a Javascript variable as to assign it's value to a TT variable? The scenario would be that from within the materialized template to extract value pairs from DOM elements like sliders,select groups etc,serialize them and save the resulting string into a cookie: <script> var getvalue = $( "#Brand").find(":selected").parent("optgroup").attr("label"); jsvar = {Brand:getvalue}; jsvar = JSON.strignify(jsvar); [% SET session.ttvar= jsvar ]% </script> Imagine going through a series of elements,capturing the values which can be used later on as parameters to a POST call i.e {Brand:...,Price_from....,Price_to:...} since they would be saved in a cookie which would be valid for the rest of the session, they could be reused by the same or another route for purposes of for example reinstating or remembering the previous state after the back button of the browser is hit Of course, that could be done with an Ajax call but been thinking of alternative ways So the problem here is how do you escape out of the TT context and inject temporary Javascript context in [% SET session.ttvar= jsvar %] ,so that jsvar gets assigned to ttvar ?

3 2

Trial bugfix release of Dancer 1 on its way to CPAN
by Yanick Champoux 07 Sep '15

07 Sep '15

Hi all, A small bugfix release of Dancer 1 has been punted to CPAN. As usual, if nothing horrid is reported within 5 days, it'll be promoted to a stable release. Also as usual, thanks to all involved. Y'all rock harder than Hawaiian volcanos. Joy, `/anick 1.3141 2015-09-07 [ BUG FIXES ] - Dancer::Logger::Abstract now always try to convert to the configured charset. (GH#1125, ironcamel) - Fix test that was failing on Windows because of platform-specific directory separators. (GH#1122, nanis) [ STATISTICS ] - code churn: 11 files changed, 52 insertions(+), 37 deletions(-)

1 0

Digest Authentication and Plack::Test and get the user in Dancer2
by Arjan Widlak 06 Sep '15

06 Sep '15

Hi, Is it possible to test Digest Authentication with Plack::Test without starting a live server? With a live server I can do this: | my $browser = LWP::UserAgent->new();|| || $req = HTTP::Request->new( GET => 'http://localhost:5000/' );|| || $browser->credentials(|| || "localhost:5000",|| || "ZZZZZZ",|| || 'arjan(a)xxxxxx.nl' => 'xxxxxx'|| || );|||| || $res = $browser->request( $req );|| || ok( $res->status_line eq '200 OK', 'success with login with credentials' );| And in my Dancer2 app I get: |get '/' => sub {|| || my $dsl = shift;|| || my $user = $dsl->app->request->user;| Is it possible to do something like: my $test = Plack::Test->create($app); |my $req = GET '/mYtQ2EeQthcclMhsqDZTbVcggwX9kJDo';|| ||$req->header( "Accept" => "application/json" );|| ||$req->header( "Host" => "localhost" );|| ||$req->header( "Authorization" => 'Digest username="arjan(a)xxxxxx.nl",|| || realm="ZZZZZZ",|| ||nonce="dcd98b7102dd2f0e8b11d0f600bfb0c093",|| || uri="/",|| || qop=auth,|| || nc=00000001,|| || cnonce="0a4f113b",|| ||response="6629fae49393a05397450978507c4ef1",|| ||opaque="5ccc069c403ebaf9f0171e9517f40e41"');|| ||my $res = $test->request( $req );| And get the user in Dancer2 in the same way: |get '/' => sub {|| || my $dsl = shift;|| || my $user = $dsl->app->request->user;| Where does Dancer2 get the user that is returned with $dsl->app->request->user? I had a hard time finding this in Dancer2::Core::Request.pm, where it's in the documentation. Kind regards, Arjan.

2 1

New Dancer2 release en route to CPAN: 0.162000
by Sawyer X 06 Sep '15

06 Sep '15

Yet another Dancer2 release hitting CPAN as we speak, all the way from Granada, Spain, courtesy of YAPC::EU 2015. We've made a few interesting changes, highlights of which I would like to share with you. **Fixes** * Escaping file paths in regexes. * Handle response in before hook correctly when serializer available. * Correctly validate *all* options in route definition. * Custom error templates fixes, including in before hooks. * Unmask exceptions thrown by serializers. **Enhancements** * Major optimizations! Dancer 2 is now at least as fast as Dancer 1. We're continuing work on optimizing it. If you have use-cases you would like us to take a closer look at, just let us know! * Better stack trace display. * Correctly set response content via "halt" keyword. * Switch to HTML5 templates! * Streamline and optimize serializer helpers (`to_json`, `from_json`). **Thanks** We want to thank our lovely contributors for this release (in alphabetical order): A. Sinan Unur, Achilles Kars, Andy Beverley, Dmitrii Tcyganov, Gabor Szabo, Kadir, Nick Tonkin, Patrick Zimmermann, Tina Müller, Vernon, and, of course, our core devs involved in this release: Alberto Simões, Mickey Nasriachi, Russell Jenkins, Sawyer X. **Future plans** We intend to introduce one major change and deprecate unsafe behavior. We have a branch ready (which will be merged only *after* this release) that introduces three new keywords: `query_parameters`, `body_parameters`, and `route_parameters`. These will return values that make it unnecessary to validate whether you received a single value or multiple values. It's a change we've wanted to introduce for a while now. We also plan to deprecate the ability to set route parameters that undermine two specific features in route matching: splat/megasplat and regex captures. Unless you have `:splat` or `:captures` placeholder variables in your route definitions, you will not even notice. Have a great dance, :) Sawyer and the Dancer Core Dev Team.

1 0