MVC: Do we really need to name Surface Controllers "Surface"
I've heard that the recommended naming convention for surface controllers is to include Surface in the controller name (i.e. AccountSurfaceController).
In practice, I've never had a problem just sticking with the standard (i.e. AccountController), however can someone enlighten me as to why Surface needs to be included in the controller name? When you start build up a lot of controllers the View folder can look a bit ugly.
MVC: Do we really need to name Surface Controllers "Surface"
I've heard that the recommended naming convention for surface controllers is to include Surface in the controller name (i.e. AccountSurfaceController).
In practice, I've never had a problem just sticking with the standard (i.e. AccountController), however can someone enlighten me as to why Surface needs to be included in the controller name? When you start build up a lot of controllers the View folder can look a bit ugly.
Thanks
Kev
Nope. :-)
We removed that limitation (which actually was only enforced when you were trying to include surfacecontrollers in plugins).
Thanks Sebastiaan for responding so quickly :-)
I guess the scaffold template thing needs updating?
Sure, but it's no crime if you still name them that way (nothing will break).
true true
is working on a reply...