Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Routine for view rendering #19

Open
alganet opened this issue Feb 18, 2012 · 2 comments
Open

Routine for view rendering #19

alganet opened this issue Feb 18, 2012 · 2 comments
Labels
feature
Milestone
Ideas

Comments

@alganet
Copy link
Member

alganet commented Feb 18, 2012

A routine that can map routes to specific rendering engines (such as template engines or serializers).
@augustohp
Copy link
Member

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

@ramsey
Copy link
Contributor

ramsey commented Mar 9, 2012

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?

@augustohp augustohp modified the milestone: Ideas May 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature
Projects
None yet
Milestone
Ideas
Development

No branches or pull requests
3 participants
@ramsey @augustohp @alganet