<div dir="ltr">You are fantastic.<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Dec 6, 2013 at 6:30 PM, Yanick Champoux <span dir="ltr"><<a href="mailto:yanick@babyl.dyndns.org" target="_blank">yanick@babyl.dyndns.org</a>></span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 13-12-06 11:22 AM, Yanick Champoux wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I can reproduce the issue with Pierre's code. Weird. I'll have a deeper<br>
look.<br>
</blockquote>
<br></div>
Urgh.<br>
<br>
So it seems that the response object is created before the serializer is set. And, even worse, it's not the response's own serializer that is set, but the global serializer for the application. Which means that we have this delightful delayed slapstick act:<br>


<br>
$ curl localhost:3000/page.json<br>
HASH(0x32fafd8)<br>
$ curl localhost:3000/page.yaml<br>
{"status":"404","title":"Error 404 - Not Found","message":"unsupported format requested: yaml"}<br>
$ curl localhost:3000/page.yml<br>
{"some key":"value","something":"<u></u>else"}<br>
$ curl localhost:3000/page.json<br>
---<br>
some key: value<br>
something: else<br>
<br>
<br>
Github issue will be created. Problem shall be solved. But only after my coffee's drained. :-)<div class="HOEnZb"><div class="h5"><br>
<br>
Joy,<br>
`/anick<br>
______________________________<u></u>_________________<br>
dancer-users mailing list<br>
<a href="mailto:dancer-users@dancer.pm" target="_blank">dancer-users@dancer.pm</a><br>
<a href="http://lists.preshweb.co.uk/mailman/listinfo/dancer-users" target="_blank">http://lists.preshweb.co.uk/<u></u>mailman/listinfo/dancer-users</a><br>
</div></div></blockquote></div><br></div>