Routine for view rendering

[alganet]

A routine that can map routes to specific rendering engines (such as template engines or serializers).

[augustohp]

This should be done by the conneg routine shouldn't?

[ramsey]

Content negotiation is the preferred way of doing this, IMO, but I suppose if the request is for .html or .json or .xml, then regardless of the Accept header, we could use a routine map to return the proper content type for the extension?

[alganet]

I think the original idea I had for this was to allow decoupling how we deal with serialization. For example, today (and 14 years ago) we detected JsonSerializable returns and used json_serialize internally. That decision could be exposed to the user instead so he/she can decide on a serializer of choice.

This is a wanted feature somehow, and it does interact with the idea of content negotiation. I'll investigate this use case further.