Controller Suffix

Is it really? I am not sure myself, but I would certainly bow to greater knowledge.

Here is an example.

A customer emails:

Found an error on www.somesite.com/reports where link doesn't work on custom report.

I know immediately that it is the reports controller. I go there and see some function

PHP Code:

$this->reports_model->get link() 


and I know immediately that is a call to the reports model function get_link. I check in there and find the error.

The alternative is:

A customer emails:

Found an error on www.somesite.com/reports where link doesn't work on custom report.

I have to check the routes first for where that link is routed to. With hundreds of routes that might not be such a simple taks. I find the route and go there and see some function

PHP Code:

$this->reports->get link() 


Is it an internal function? I check the controller and it is not. Is it a library, I check the library and in the reports_library I find a get_link function. I cannot find an error with that and scratch my head for a while. Then I discover it is a model call, so I check the model and find another get_link function and there is the error finally.

Personally I stick to the magic routes for CI! Admittedly the example above is completely fictitious.

So in using a framework that provides a routing methodology, is it really best practice to define every route?

Best wishes,

Paul