Hi guys. My two cents : the fact the old behavior broke some serializers is indeed a problem. Also, given that D2 provides a clean scoping (thanks Apps!) it's not such a problem we're now stricter. If you want both, just put the serializers in an app and you're done. Bonus side effect : your code is now cleaner :-) So, to me, this is the right thing to do for D2. Le mar. 27 oct. 2015 18:35, WK <wanradt@gmail.com> a écrit :
2015-10-27 14:35 GMT+02:00 Russell Jenkins <russell.jenkins@strategicdata.com.au>:
Sawyer and I briefly discussed if this should be core functionality during the conference. We decided to release it as a plugin and review moving it to core if other Dancers find this functionality useful.
I really liked this feature in D1, even I did not use it. So I like it in D2 (as plugin) too. It brings back flexible possibility of content negotiation. I missed it (theoretically). But is D2 aimed for webapps or webservices? If equally for both, then it should find it's place in core, IMHO.
Wbr, -- Kõike hääd,
Gunnar _______________________________________________ dancer-users mailing list dancer-users@dancer.pm http://lists.preshweb.co.uk/mailman/listinfo/dancer-users