Re^2: Dancer2 parameters understanding and usage

Hello 1nickt++ and ++1nickt (even if we know this leads to an undefined behaviour..)

> The main problem you have with the posted code is that you are trying to retrieve the value of your body parameters with the method for retrieving query parameters.

> When you get data POSTed from a form, it's transported in the body of the HTTP request (in general, not specific to Dancer). Query parameters are those passed as the query string, e.g. /form?search_for=truth.

OMG i completely misunderstood the terminology and I repeat, docs have not helped me a lot. I was sure (nothing worst to be convinced of something wrong) that query parameters were these passed via POST and body ones were something defined in the body of the routes, like private variables..

My approsimative understanding of the web mechanism (i'd say underlying form) does not revealed immediatly to me that query parameters was for things passed via query in the URL like /form?search_for=truth and that body ones were reffered to the body of the incoming POSTed request.

I also misunderstood route parameters at first glance: i've tested them many times with URLS like /form?search_for=truth before understending that the correct way is:

get '/routeparam/:name?' => sub {
        # ok http://127.0.0.1:5000/routeparam/here_my_name
        "Hey " . route_parameters->get('name') . ", welcome here!";
    };
[download]

All your others suggestions and contributions are precious for me.

I have already read all the docs you linked above but i'm even more convinced now that basic docs need some integrations for not already web developpers. As soon as I have got all these basic dance moves I'll make a pr for the doc part of Dancer2 probably for the main manual.

There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.

Comment on Re^2: Dancer2 parameters understanding and usage Select or Download Code

Replies are listed 'Best First'.
Re^3: Dancer2 parameters understanding and usage by 1nickt (Canon) on Nov 29, 2017 at 18:08 UTC
Just to be clear about route parameters. You can define any part of a URL path as a parameter. You don't need a 'static' part to prefix a param, although a lot of apps, particularly REST APIs, do that. You can also use route and query (and even body) params together. For example: `get '/foo/:name/bar/:age/:occupation' => sub { return '<pre>'.Dumper({ params }).'</pre>'; };` [download] If the user requests the following URL: `http://localhost:5000/foo/Discipulus/bar/42/student?country=Eataly&cit +y=Roma` [download] The app displays in the browser: `<pre>$VAR1 = { 'name' => 'Discipulus', 'age' => '42', 'city' => 'Roma', 'occupation' => 'student', 'country' => 'Eataly' }; </pre>` [download] Also see: Dancer2 Advent Calendar: New Parameters Keywords. (The Dancer2 Advent Calendar is a great source of documentation and examples.) The way forward always starts with a minimal test.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^3: Dancer2 parameters understanding and usage
by 1nickt (Canon) on Nov 29, 2017 at 18:08 UTC

Just to be clear about route parameters. You can define any part of a URL path as a parameter. You don't need a 'static' part to prefix a param, although a lot of apps, particularly REST APIs, do that. You can also use route and query (and even body) params together. For example:

get '/foo/:name/bar/:age/:occupation' => sub {
    return '<pre>'.Dumper({ params }).'</pre>';
};
[download]

http://localhost:5000/foo/Discipulus/bar/42/student?country=Eataly&cit
+y=Roma
[download]

<pre>$VAR1 = {
          'name' => 'Discipulus',
          'age' => '42',
          'city' => 'Roma',
          'occupation' => 'student',
          'country' => 'Eataly'
        };
</pre>
[download]

Also see: Dancer2 Advent Calendar: New Parameters Keywords. (The Dancer2 Advent Calendar is a great source of documentation and examples.)

The way forward always starts with a minimal test.

[reply]
[d/l]
[select]