On Mon, Feb 15, 2010 at 7:48 PM, Yehuda Katz wrote:
> The catch-all route let to a series of faulty patterns such a
> hide_action and verification. At it's core, the router is the
> appropriate place to limit request that go onto the controllers.
Agreed. Many a 2.x production app spews exception
The catch-all route let to a series of faulty patterns such a
hide_action and verification. At it's core, the router is the
appropriate place to limit request that go onto the controllers.
In this case, removing the default route allows us to simplify the
explanation of how you should go about "h
I agree with Trey. People learning Rails should be learning the
conventions, not the exceptions. As for the learning curve, I think it
is simple enough to generate a scaffold.
Allen Madsen
http://www.allenmadsen.com
On Mon, Feb 15, 2010 at 8:53 PM, Trey wrote:
> Hey Anthony,
>
> Great observat
Hey Anthony,
Great observation here. The only thing I would say is to define
"beginners" and how you want to teach them. We're all being pushed
towards a more RESTful design - both by Rails and by web development
in general. So it seems that a framework has to make a decision - do
we make it eas
