[TYPO3-team-core-v5] Check your pending changes...

[Bastian Waidelich]

Bastian Waidelich wrote:

>> Default actions could be renamed to "indexAction"

> Hmm, probably. Unfortunately we'd have have to do the same for the 
> controller, so we end up with these conventions (1):
> [...]
> F3::MyPackage::View::Index::IndexHTML.php
> F3::MyPackage::View::Pages::ShowHTML.php
> 
> Or we change the path conventions for the views, which allows us to keep 
> the "DefaultController" at least (2):
> [...]
> F3::MyPackage::View::DefaultIndexHTML
> [...]
> 
> If you ask me, I'd go for (2).
> What do you think?

Yes, I'd go for (2) aswell, though it leads to long and dizzying view 
class names like "IndexIndexHTML".. But I can't think of a better 
solution for now.
Let's hope that PHP will allow reserved keywords in class names in the 
stable release (after all namespaces should make this possible) - Well, 
it doesn't seem like they're up for it: 
http://bugs.php.net/bug.php?id=43048.


> And while we're at it: A rather time-consuming change but probably worth 
> it would be to change the naming conventions again so that the exception 
> for all uppercase abbreviations is not allowed anymore:

personally, I think singYMCALoudly() is easier to read than 
singYmcaLoudly() ;)
Is there any technical reason why we should change this?


> (old)  $myTYPO3Page
> (new)  $myTypo3Page

Now that is against the TYPO3 style guide *g

Bastian