Dávid Kovács

Update: OK, I think a got it. The whole thing is in D2::Core::Response.pm .When not using a 'set serialzer => something' (https://metacpan.org/pod/distribution/Dancer2/lib/Dancer2/Manual.pod#Serializers1) , i.e. when manually serializing the output in...

See my updated post above (the first half), I think the problem is described there. #TODO write a Dancer2::Unicode manual?

Well the 'auto-serializer' uses the 'serialize' method directly, so yes, turning utf-8 to 0 by default when using to_/from_\* methods would be an option. But there could be problems, when...

BTW in your case using "set serializer => 'JSON';" solves the problem; so another option is to document this behaviour and state, that to_json should NOT be used to return...

Yeah, good point. I have no idea what would be best in this case.

Yeah. 'use utf8;' only tells Perl, that the source code (the .pm file) is in utf-8. In this case this use statement is important, because you have the 'Alberto Simões'...

Yes, indeed, it is. But if we set utf8 to 0 by default, it would be counter-intuitive to set { utf8 => 1 } elsewhere. There is no one good...

It seems that there are a few scenarios where utf8 serialization is a problem: ``` get '/' => sub { my $x = to_json(params('form_data')); $obj->process($x); return template 'success'; }; get...

For fun I'm tackling this issue right now. I was thinking about the possibilities to implement it. I was thinking about modifying some D2::C::DSL methods, namedly GET, POST, PUT, PATCH,...

`route "home" => get '/' => sub {}` or `uri "home" => get '/' => sub {}` I'd read it like: the 'value' of the 'home' route/uri is this get...