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

State of Dancer2 debugging support?
by Warren Young 10 Feb '14

10 Feb '14

Do the 'show_errors' and 'traces' config settings work in Dancer2? I ask because I have both set in my environment/development.yml file, but I am still seeing it render 500 errors using public/500.html, rather than the custom error screen the docs claim. I have verified that the development.yml file is being read by putting unparseable junk in it, which prevents my app from starting, as expected. Also, I put this at the top of the route handler I'm having trouble with: debug "Dancing on the ", (config->{'environment'}), " dancefloor."; It does say "development". By the way, the 'startup_info' configuration flag is documented as showing the "dancefloor" in the banner, but I only get this here: Dancer2 v0.11 server 19360 listening on http://0.0.0.0:30000 I wouldn't have needed to add this 'debug' call if the banner did show the dancefloor as documented. Here are my 3 config files, slightly sanitized: config.yml: appname: "MyApp" charset: "UTF-8" environment: "development" port: 30000 session: "simple" template: "Xslate" engines: session: Simple: cookie_name: "myapplogin" cookie_duration: "30 days" session_duration: 3600 environments/development.yml: logger: "Console" warnings: 1 show_errors: 1 startup_info: 1 traces: 1 engines: logger: Console: log_level: core environments/production.yml: log: "warning" logger: "File" warnings: 0 show_errors: 0 route_cache: 1 Not to pile on, but it seems that changing 'environment' to 'production' in config.yml doesn't do anything. The errors still keep going to the console instead of a log file, and the verbosity level doesn't drop to 'warning'. The 'debug' line I added to my problem route does show up, and it says 'production'. The fact that this happens at 'debug' level corroborates my claim that the verbosity level isn't changing.

1 0

Dancer app in production on Starman : Dancer::Plugin::Database Child process cannot use database handle created in parent
by Anthony Milan 10 Feb '14

10 Feb '14

Hi, I tried to deploy my little app with Starman: plackup -E deployment -s Starman -p 5001 --workers=2 -a bin/app.pl I had this error: Child process cannot use database handle created in parent I used Dancer::Plugin::Database to manage database In this thread: http://lists.preshweb.co.uk/pipermail/dancer-users/2011-July/001681.html I read that Dancer::Plugin::Database ensure that handles are not shared between processes/threads. Most probably, I do something wrong :( Thanks for any help, -- Anthony Milan

1 1

updating a form
by Gert van Oss 10 Feb '14

10 Feb '14

Hi, I’m trying to build a small app to comment on images. Probably I’m almost there but currently stuck with updating a ‘file.yml' by a html-form. I’ve made two routes (shown below) “get ‘/:id/edit’ for showing the form with the particular image to comment on. When hitting save the ‘post ‘/edit’ will be called. My problem is that the post route doesn’t have the $id initialised. Is there someone around who can tell me how to solve this or point to me what I’m doing wrong? Thanks, Gert The structure is an AoH. The file.yml is like --- - collection: '' description: good id: 0 imgf: photo.jpg tags: '' - collection: '' description: '' etc.. ————end of yaml #--------------------------------------------------------------------- # # get EDIT # #--------------------------------------------------------------------- get '/:id/edit' => sub { my $filename = Dancer::FileUtils::read_file_content( Dancer::FileUtils::path( setting('appdir'), 'myImages.yml' ) ); my $data = from_yaml $filename; my @data = @{$data}; #print Dumper \@data; my $id = param('id'); template 'edit', { data => $data[$id], id => $id, }; }; #--------------------------------------------------------------------- # # post EDIT # #--------------------------------------------------------------------- post '/edit' => sub { my $data = get_AoH_imagelist(); my @data = @{$data}; my $id = param('id'); $data[$id] { description}= params->{description} ; #$data[2] { description}= params->{description} ; # this works but then all descriptions end up in the third group of hashes. my $filename = "myImages.yml"; write_file $filename, to_yaml($data); redirect '/'; };

6 8

Applicability of Dancer and Dancer vs. Dancer2
by Lutz Gehlen 09 Feb '14

09 Feb '14

Hello everybody, I tend to think that the following questions have been asked before, but I my search has been unsuccessful. So if someone could point me to existing documentation or mailing list threads I'd be happy as well. 1) I am trying to decide whether to use Dancer for a small to middle size web application. The key advantages that seem to keep coming up when people talk about Dancer is simplicity and light weight and that people recommend it for small or toy applications. That raises the question if there is a price to pay for this simplicity and light weight. So from your point of view, are there any important features missing or in general is there any reason not to recommend Dancer for serious and/or not-so-small applications? 2) The second question I am facing is whether to use Dancer or Dancer2. I know that Dancer2 is a OO rewrite of Dancer, but I couldn't figure out how the two relate to each other with respect to the devoloping community. Intriguingly, the webpage perldancer.org does not seem to mention Dancer2 at all. More specifically: a) Are Dancer and Dancer2 developed by the same people? b) Is Dancer2 supposed to supersede Dancer? c) Is Dancer more mature than Dancer2? d) How do the two compare to each other with respect to performance? e) In general, are there any reasons to prefer one over the other except my taste for procedure or object orientation? Thanks a lot and best wishes, Lutz

3 3

How do you measure code coverage?
by Иван Бессарабов 04 Feb '14

04 Feb '14

I have a small Dancer1 app and I have started writing tests for the web part. I used to write unit tests, but I have never written tests that test web component. With Dander::Test the task of writing tests is very simple, thank you for that module. But I don't understand one thing. I'm using Devel::Cover to find out what I haven't tests. It works fine with my application model that is created without Dacner, but it does not work for the Dancer routes. Devel::Cover does not create any metrics for such code: any ['get', 'post'] => '/login' => sub { ... } Devel::Cover shows that all my Dacner code is 100% coverd, but this is not true. So this tool does not answer the question what is tested and what is not. So my question is how do you measure coverage of code that is tested?

2 3

Dancer v1.3121 on its way to CPAN
by Yanick Champoux 02 Feb '14

02 Feb '14

Hey everybody, A new release of Dancer is making its way to CPAN as we speak. The changelog is below. As usual, mucho thanks to the contributors and bug reporters and everybody who made the release possible. Y'all rock. :-) Joy, `/anick 1.3121 2.02.2014 [ ENHANCEMENTS ] * GH #994: change heuristic so that 'application/vnd.openxmlformats-[...].sheet' is not recognized as text. (Skeeve) * GH #987: get_current_session() now accepts option 'no_update'. (Lee Carmichael) [ DOCUMENTATION ] * GH #983: Correction of various typos. (Akash Ayare) * GH #981: Add synopsis to Dancer::Request::Upload. (smashz) * GH #985: Change mentions of 'PerlHandler' to 'PerlResponseHandler' (Xaerxess)

1 0

Complex Query ?
by Hugues 31 Jan '14

31 Jan '14

Hello I use dancer 1 with with mysql @resultCC = database('db')->quick_select('ClientContrat', { NumContrat => { like => "$search%" } }, { limit => 10 } ); I send @resultCC to my template tt and it's work well I would like to pass complex query my $sql ="SELECT Client.CodeClient, Client.NomClient,Client.Ville, ClientContrat.NumContrat FROM Client INNER JOIN ClientContrat ON (Client.CodeClient = ClientContrat.CodeClient) WHERE Client.CodeClient LIKE '%" .$search. "%' LIMIT 10"; I do not find solution to use current mysql connection , and quick_select ? ( it 's ok only if I create new connection with , connect, prepare execute ....) what is the best way to do that ? thanks Hugues.

3 5

"use Dancer2" interferes with package exports
by Warren Young 27 Jan '14

27 Jan '14

Consider this trivial module, Foo.pm: package Foo; require Exporter; our @ISA = qw(Exporter); our @EXPORT = qw(foo); use Dancer2; sub foo { map { "You gave me '$_', right?" } @_; } 1; ...and this trivial test program: #!/usr/bin/env perl use Foo; print join "\n", foo("foo", "bar"); If you run it, it will complain that &main::foo is undefined. Yet, it is unconditionally exported from package Foo by Exporter, since we've used @EXPORT. (The symptom doesn't change if you use @EXPORT_OK and import &foo explicitly, though.) The fix is easy: comment out the "use Dancer2" line. Why does that help? Why is Dancer2 roaching my module's exports list? Does it have something to do with the way Dancer exports DSL keywords into the global namespace? This is not a real solution, anyway. There is a real "Foo" module in my program that does useful work, and when I pound out the "use Dancer2" line in that module, all of my static content stops being served. Dancer tries to treat everything like a route. It's like the appdir setting isn't getting defined correctly. I tried to test that guess, putting this in one of the route handlers: debug "APPDIR: ", Dancer2::Config::setting('appdir'), "\n"; That just gets me an undefined subroutine error in the browser. I checked Dancer/Config.pm to make sure that routine really exists, as the docs claim, and it does seem to. Is this what you guys mean by "alpha"? :)

3 8

How to get the path or name of a template in a hook before the template is rendered
by Christoph Huhn 27 Jan '14

27 Jan '14

Hello fellow Dancers... I'm using Dancer 1.3. I need to add the path (relative to views directory) or at least file name of the template about to be rendered to the template tokens hash passed to this template. I don't want to replace the template set by the route handler, so a read only solution for the template name would be OK. I was hoping to do this with a before_template_render hook in a plugin, but it looks like that's impossible right now, because the hook only get's passed the tokens, not the filename. Then I tried a solution via Template Toolkits META template.name in my layout template, but that doesn't work either, because template.name is the layout template, not the content template. After checking the Dancer docs I found out that Dancer is not using TTs WRAPPER, so that's not possible. I could add the META to my content template, but the I'd have to change all of my templates and every template call in my route handlers (wich are quite a lot by now). I've searched the docs, googled quite a lot of Dancer related websites and browsed through the code of some Plugins, but haven't found a "official" way to get the template file path or file name. I've seen a solution (in Dancer::Plugin::DebugToolbar) that iterates over %INC and overrides every render method of any Dancer::Template::* module it can find. That would work, but it feels kinda wrong to me. There should be an easier solution to this, than digging in the guts of core or other plugin modules. Any suggestions are most welcome. Best regards, Chris

1 0

Confused about types and globals
by Warren Young 23 Jan '14

23 Jan '14

I'm trying to get my head around Dancer2, and am having trouble because it doesn't look entirely like Perl to me. For example: get '/foo/*' => sub { .... What is "get", exactly? I assume it is a function that takes a string and a coderef, and you're taking advantage of Perl's optional parentheses and fat comma to create a Perl-based DSL. The problem is, I can only find examples and tutorial docs, not a reference that outright confirms that, so I'm left with this uneasy feeling that I don't truly understand what's going on here yet. I tried to answer this myself before posting. I thought it might be a package-global function, but there is no "sub get" in Dancer2.pm. I also tried looking for a POD reference page on metacpan that explains this, but it ends up being a fully manual search since the metacpan search engine can't help with a generic term like 'get', and there are ~50 namespace pages to dig through. Another example: context->destroy_session The only way I can think of for that to work without a sigil is for 'context' to be another global (?) function that returns an object reference, rather than be an object reference itself. There is no "context" in Dancer2.pm, so I'm left wondering where it comes from. In one place, the tutorial docs say it is passed in to a "before" handler, while in other places it is assumed that you can just *use* this entity without having one passed into the route handler. I care about this because I'm trying to port a fairly complex app from Apache::ASP to Dancer2, and this app is already broken up into many separate modules. Because of this, the tutorial docs' assumption that I am writing all of my server-side code within the top-level module's route handlers doesn't apply. I'm not going to consolidate dozens of modules of code into this one module, just to solve the namespace problems. That just trades one problem for another. Ideally, I want my top-level module to be as small as possible, doing little more than set up the route handlers, delegating all the real work to other modules. To do that, I need to know where these objects come from, their exact data type, and which package's namespace they live in. Then I'll know how to reference them or pass them around to the modules that do the work in my app.

5 6