August 2017 - dancer-users - lists.preshweb.co.uk

Re: [dancer-users] How do you minimise code in Main.pm? (looking for good Dancer2 patterns)
by Scott H 23 Aug '17

23 Aug '17

So I think the advent reply was pretty good, I wish that was in the docs as a way to do it. I started with Dancer 1 a few years ago and the tutorials and cookbook were a good start but I ran into your problem as well. I had to find a way to split up my code so my main app.pm was not just loaded with stuff. I took more of a MVC approach and made in my libs lib/models and lib/controllers folders and in my controllers put my routes for different things so I would have authentication.pm, dashboard.pm, etc.. on my models stuff I will have more of a lib perl modules scenario where my libraries and their functions exist. Such as Users.pm, Logging.pm etc... In my main app.pm I will call use controllers::dashboard; use controllers::authentication; my controllers will then use the model libs with use model::libname and then pull any functions they need out to perform the controlling of the view and then like a route load the view at the end. It works good enough for me as its laid out nice. I would consider the advent way by loading the functions directly to the route. Hopefully this gives you another idea of how to lay it out. -Scott

1 0

How do you minimise code in Main.pm? (looking for good Dancer2 patterns)
by Nathan Bailey 22 Aug '17

22 Aug '17

Hi all, I get the sense that we are using Main.pm very poorly and a bit of Dancer2 architectural insight would greatly improve the quality of our code. What is the best pattern for the breakdown between perl module/Dancer2 route handler/TT file? For example, if you have a sub-system for administrators that manages the fees tables and reports, would you put these into separate route handlers? eg. ReportsHandler.pm => Route handler for reports - Instantiates an instance of Reports.pm in it's "before" hook so we only need to do this once (or in the module itself?) - the 'view' and 'save' routes call the appropriate 'get' and 'set' methods for that table in Reports.pm and a separate handler for Fees, with an overarching Main.pm route handler that largely deals with mainstream userspace routes (any significant user workflows get their own router handler module like ReportsHandler and FeesHandler)? Ideally, I'd like all our code in the perl modules, with the route handler doing nothing but dispatch (with error handling) and the TT doing basic interface presentation. But at the moment, each route handler is 20-30 lines long - I think they should be ~5 lines long or less. An exemplar Main.pm + TT file would be very helpful! cheers, Nathan

2 1

Progress bars
by Clive Eisen 13 Aug '17

13 Aug '17

Hi I have a long running route that I would like to give feedback from via a progress bar I have installed https://github.com/shumphrey/Dancer2-Plugin-ProgressStatus <https://github.com/shumphrey/Dancer2-Plugin-ProgressStatus> to test but the demo jumps from ~2% to 100% after 30 seconds Is the demo at fault or the plugin - and in either case does anyone have a working progress bar that uses a callback for updates? TIA -- Clive Eisen GPG: 75056DD0

1 1

Issue with plugin_setting
by Tony Edwardson 03 Aug '17

03 Aug '17

Hi All I am trying to write a Dancer2 Plugin to handle OpenAPI (Swagger2) configs and I want to configure the plugin via config as usual. In my config.yml, I have :- plugins: OpenAPI: configfile: "openapicfg.yml" my Dancer2::Plugin::OpenAPI.pm looks like this:- package Dancer2::Plugin::OpenAPI; use Dancer2::Plugin; use Dancer2::Plugin::OpenAPI::Core; use Data::Dumper; register OpenAPI => sub { my $self = shift; my $plugin_conf = plugin_setting(); print Dumper { pluginconf => $plugin_conf }; ......... }; and Dancer2::Plugin::OpenAPI::Core has :- package Dancer2::Plugin::OpenAPI::Core; use Moo; use JSON::Validator::OpenAPI; use Data::Dumper; has 'apiconfig' => ( is => 'rw', reader => 'get_apiconfig', writer => 'set_apiconfig' ); sub BUILD { my $self = shift; my $config = shift; my $val = JSON::Validator::OpenAPI->new; my $url = $config->{url}; my $spec = $val->load_and_validate_schema($url); $self->set_apiconfig($val->schema->data); return $self; } 1; My App has this :- package MyApi; use strict; use warnings; use Dancer2; use Dancer2::Plugin::OpenAPI; my $apiconfig = OpenAPI->get_apiconfig; I am using Dancer2 version 0.204001 on Centos 7.3.1611 and Perl 5.16.3 When I run this - the plugin config is empty $VAR1 = { 'pluginconf' => {} }; Anyone got any idea what I am doing wrong here ? Thanks Tony

1 0