OX and routing: how to declare something like /api/action.:format

mascip has asked for the wisdom of the Perl Monks concerning the following question:

Hi there, I'm trying out OX.

A bit of context: until now I've used Dancer. I want to try OX and see how I like it. I have read the whole OX advent calendar 2012 and understood most of it (I'm not very familiar with Bread::Board yet).

I have a RESTful API, and I'm trying to do something a bit similar to Dancer::Plugin::REST: send something different to clients depending on the format requested. More specifically I want to send JSON back on /api/action.json, YAML on /api/action.yaml, or a prettified JSON in a HTML template on /api/action.

So far my idea is to match all those with a single route. In Dancer I would do:
/api/action.:format
And then my View object would render something that depends on the request's path: that's dead simple with OX.

My problem is that the /api/action.:format route doesn't seem to match anything. Indeed, I don't see anything similar in the Path::Router documentation, which OX is based on. Does it mean it's impossible to do what I want with OX? OX seems powerful, so I guess not.

What could be a solution to my problem?

Comment on OX and routing: how to declare something like /api/action.:format Select or Download Code

Replies are listed 'Best First'.
Re: OX and routing: how to declare something like /api/action.:format ($DEBUG++ MANIFEST) by Anonymous Monk on Dec 08, 2013 at 14:56 UTC
My problem is that the /api/action.:format route doesn't seem to match anything. Turn on debugging :) https://metacpan.org/pod/Path::Router#DEBUGGING Read more... (2 kB) So something something "components" something What could be a solution to my problem? MANIFEST :) http://search.cpan.org/dist/OX/MANIFEST, http://search.cpan.org/dist/Path-Router/MANIFEST, http://search.cpan.org/dist/Path-Dispatcher/MANIFEST, https://metacpan.org/source/DOY/OX-0.13/t/apps/Counter-Over-Engineered-Sugar/lib/Counter/Over/Engineered/Sugar.pm https://metacpan.org/source/DOY/Path-Router-0.12/t/006_match_w_targets.t https://metacpan.org/source/DOY/Path-Router-0.12/t/003_messy_paths.t Hmm, so the dot is the dot dot dot not slash slash slash ... what? update: I don't see that it can be done (seems to assume / decides what can be :variable ) ... I would consult module author for this bug-or-wishlist item , or try some other router This is why I think that Read more... (2 kB) can't fake it, so bug Read more... (868 Bytes) And I'm bored again	[reply] [d/l] [select]
Re^2: OX and routing: how to declare something like /api/action.:format ($DEBUG++ MANIFEST) by mascip (Pilgrim) on Dec 08, 2013 at 16:14 UTC
Wow, thank you! I never think about checking the tests, good thinking. I've found this solution which works: `my @extensions = ('', '.json', '.yaml'); route "/api/action$_" => 'controller.action' for @extensions;` [download] It's not elegant but I might figure out a way to make it look nicer in the future.	[reply] [d/l]
Re^3: OX and routing: how to declare something like /api/action.:format ($DEBUG++ MANIFEST) by Anonymous Monk on Dec 08, 2013 at 16:31 UTC
:) broooforce naturally :) in a way this is nicer for it makes explicit and discoverable (introspection) of whats available	[reply]
Re^4: OX and routing: how to declare something like /api/action.:format ($DEBUG++ MANIFEST) by mascip (Pilgrim) on Dec 08, 2013 at 21:18 UTC
Re^5: OX and routing: how to declare something like /api/action.:format ($DEBUG++ MANIFEST) by tobyink (Canon) on Dec 08, 2013 at 23:45 UTC
Some notes below your chosen depth have not been shown here