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

New release of Dancer2::Plugin::Auth::Extensible
by Stefan Hornburg (Racke) 17 Mar '15

17 Mar '15

Thanks to the copious amount of pull requests from Henk van Oers, Andrew Beverly and Gabor Szabo there is a new release of Dancer2::Plugin::Auth::Extensible on CPAN. After bundling up these bug fixes and little improvements in a release, I'm going to further review Andrew's work on creating user, updating users and password reset. To make this even better, we need help with testing the distribution and write tests that covers all aspect of this module. Regards Racke -- Modern Perl, Dancer and eCommerce consulting.

2 1

Devel::Cover and Dancer
by Gabor Szabo 17 Mar '15

17 Mar '15

When last time I ran the tests of my Dancer2 based app through Devel::Cover it did not provide any report for the routes. If I use names subroutines and set them as get '/' => \&serve_index; sub serve_index { } then Devel::Cover takes those subs into account. Do you know how can I convince Devel::Cover to report properly even with anonymous subs? Gabor

3 2

Updates to Dancer2::Plugin::Auth::Extensible
by Andrew Beverley 14 Mar '15

14 Mar '15

Hi guys, I mentioned a while ago that I was hoping to add features into Dancer2::Plugin::Auth::Extensible from https://github.com/abeverley/libdancer2-plugin-auth-complete-perl I'm going to hopefully look at this properly tomorrow, with the aim to migrate one of my projects across. This is just a heads-up, as I'd like to get this done pretty quickly. As a taster, I'm hoping to add the following functionality: * Password resets * Generate fixed passwords * DBIC support * Ability to update user details (providing backend supports it) Does anyone have any immediate comments on the above? Presumably the best thing for me to do is create PRs in Github? Thanks, Andy

3 10

Auto-serialising of parameters
by Andrew Beverley 14 Mar '15

14 Mar '15

Hi guys, In the code for Dancer2::Plugin::Auth::Extensible I see the following: # For security, ensure the username and password are straight # scalars; if the app is using a serializer and we were sent a # blob of JSON, they could have come from that JSON, and thus # could be hashrefs (JSON SQL injection) - for database providers, # feeding a carefully crafted hashref to the SQL builder could # result in different SQL to what we'd expect. That all makes sense. However, from what I understand, auto-serializing now happens either for all request or for none. Therefore, are these sort of checks required when running a recent version of Dancer2? Or is it just the case that they should remain there in case an older version of Dancer2 is being used? Thanks, Andy

1 0

Calling plugin_setting from a plugedin keyword
by Henk van Oers 11 Mar '15

11 Mar '15

In Dancer2::Plugin::Passphrase on line 75 I have: my $settings = plugin_setting(); Keyword 'plugin_setting' is exported by Dancer2::Plugin. In an app I can use the keyword 'passphrase' and it's in the dsl. In an other plugin I want to use the 'passphrase' keyword. package Dancer2::Plugin::Peek; # ABSTRACT: Peek around use Dancer2::Plugin; use Data::Peek; sub peekplugin { my ($dsl, @args) = plugin_args(@_); my $phrase = $dsl->passphrase( 'my password' )->generate->rfc2307; $dsl->var(peekphrase => DDumper \$phrase); } register peekplugin => \&peekplugin; register_plugin; 1; __END__ Yes. I can see the generated phrase in a template. But I also get: DEPRECATED: Dancer2::Plugin::Peek calls 'dsl' instead of '$dsl->dsl'. at /usr/local/lib/perl5/site_perl/Dancer2/Plugin/Passphrase.pm line 75. So, the question is: How do I call 'plugin_setting' in a D2 plugin? -- Henk van Oers

1 1

Proposed additions to Dancer2
by Snigdha Dagar 04 Mar '15

04 Mar '15

Hi everyone, Under Sawyer's mentorship, I have been working on adding new features to the current Dancer2 tutorial. Following is a brief list of the addtions that we have made as of now: 1. More HTTP verbs : '/edit' and '/delete' for editing or deleting an entry 2. User logins - enable registration of new users, created another table for user details 3. Authenticating user credentials 4. Enabling picture uploads for an entry The code-base for this application can be found in this repository - https://github.com/SnigdhaD/Dancr And the additions have been documented in this gist - https://gist.github.com/SnigdhaD/4b3b31bf950d68d9240f The work on the tutorial is still going on and it definitely requires some polishing. We also plan to add more features such as: 1. Improving the css 2. Creating user profile pages 3. Creating an API for a blog feed, showing the most recent blog posts. It will be very helpful to get community feedback on both the tutorial and application code. Please let us know if there are parts of the tutorial which aren't clear and/or can be rephrased better. If you wish to see some other feature being a part of the tutorial, please feel free to let us know. Thank you. Regards, -- Snigdha Dagar Electronics and Communication Engineering IIIT Hyderabad

1 0

Dancer2 0.159000 waiting for you on CPAN!
by Sawyer X 03 Mar '15

03 Mar '15

Hi everyone, It's been a little while since we had a release. We took longer this time because this release provides a few major improvements we wanted to mature. With 13 contributors and 23 tickets closed, I'd like to present Dancer2 0.159000. There are three major changes in this release: * Asynchronous streaming support (also known as Delayed Responses). * Cleanup of the Manual and Cookbook * Remove dependency on MIME::Types Dancer2 now supports full asynchronous and streaming responses while remaining event loop agnostic. You can use whichever event loop you want. An example for its usage can be found in our Manual, under "Delayed respones": https://metacpan.org/pod/distribution/Dancer2/lib/Dancer2/Manual.pod#Delaye…. We will provide more examples in the near future. The Manual and Cookbook have been revamped, thanks to the work of Snigdha Dagar, our OPW (Outreach Program for Women) contributor. This results in cleaner, clearer, and accurate documentation. The removal of MIME::Types allows us to maintain a smaller core at a low price. We're using the MIME support from Plack now, and if you have MIME::Types installed, we will use it as a fallback. A special thanks to anyone involved in this commit, especially the following people (in order of appearance in the Changelog): Russell Jenkins, Lennart Hengstmengel, Nikita K, pants, Daniel Muey, Dávid Kovács, Graham Knop, Sawyer X, Alberto Simões, Snigdha Dagar, Omar M. Othman, Nuno Carvalho, and Vince W. The full changelog for this release: [ BUG FIXES ] * GH #762: Delay app cleanup until errors are rendered. (Russell Jenkins) * GH #835: Correct Logic error in Logger if no request exists. (Lennart Hengstmengel) * GH #839: Correct "no_server_tokens" definition in production.yml. (Nikita K) * GH #853, #852: Handle malformed (contentless) cookies. (pants) * GH #840, #842: Ensure session data available to template engines. (Russell Jenkins) * GH #565, #847, #849: Fix HTTP Status template logic and documentation. (Daniel Muey, Russell Jenkins, Dávid Kovács) * GH #843: Add missing attributes to Moo class used in tests. (Graham Knop) [ ENHANCEMENT ] * GH #836: Support delayed (asynchronous) responses! ("Delayed responses" in Dancer2::Manual for more information.) (Sawyer X) * GH #824: Use Plack::MIME by default, MIME::Types as failback if available. (Alberto Simões) * GH #792, #848: Keywords can now use prototypes. (Russell Jenkins, Sawyer X) [ DOCUMENTATION ] * GH #837, #838, #841: Major documentation restructure. (Snigdha Dagar) (Check eb9416e9 and a78e27d7 for more details.) * GH #823: Cleanup Manual and Cookbook docs. (Omar M. Othman) * GH #828: Provide README.mkdn. (Nuno Carvalho) * GH #830: Fix typo in Session::YAML pod. (Vince W) * GH #831,#832: Fix broken link in Session::YAML pod. (Vince W)

2 2