I subscribe to the view that restful controllers are not a good idea and should be avoided altogether: routes should be explicit. Resource controllers are okay because they're predictable, if a resource is registered a developer can look at the routes and understand what is happening, that isn't possible with a restful controller: a developer is forced to dig through the various controllers. If your controller isn't for something that can be considered a resource (and only needs a single method for example) then you can register the routes on their own, you don't need to push the routing responsibility onto a controller.
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community