exactly, that's the downside to it. it's really nice to have /controller/method/param/param routing out of the box, so the speed of 0 to MVP is quick, but on t

exactly, that's the downside to it. it's really nice to have /controller/method/param/param routing out of the box, so the speed of 0 to MVP is quick, but on the other side, renaming a route sucks. unless you have a list of overrides in which case, may as well just use hand written routes from the get go