Oh I see what you mean now, basically he wants ‘named routes’ which are methods based on the route. Thus if you change the route the methods will no longer exist and raise NoMethodError. (This has nothing to do with ‘a route to a controller’, though.)

We can look into making something like that in the future. For now just hardcode it.