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.

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

request.action? #843

Closed
activestylus opened this Issue May 1, 2012 · 1 comment

Comments

Projects
None yet
3 participants
@activestylus
Contributor

activestylus commented May 1, 2012

In padrino I can do request.controller but I can't do request.action - reflecting on this a bit I see why this would not be included, as it depends on us naming our routes, which a lot of people don't do. But how about a convention that when the route IS named, we have access to it from the request object?

Food for thought...

@ujifgc

This comment has been minimized.

Show comment
Hide comment
@ujifgc

ujifgc Jan 12, 2013

Member

#1004 implements it

Member

ujifgc commented Jan 12, 2013

#1004 implements it

dariocravero added a commit that referenced this issue Jan 12, 2013

Merge pull request #1004 from ujifgc/route-action
Add request.action to implement #843
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment