[TYPO3-core] More strict convention for typoscript naming

[Philipp Gampe]

Hi Dominique,

Dominique Feyer wrote:

> After a discussion with Marcus Schwemer on Twitter and the upcoming 6.0
> I think that the good time to speack about the lack of naming convention
> in typoscript.
> 
> We have a long history of weird naming in typoscript, can we found a
> solution to avoid that in the future ? Typoscript is a fantastic tools
> ... but hard to learn and if the naming is not consistent, this learning
> curve increase. That a bad thing for beginner ... and after years of
> typoscript ... i continue to loose my time with this kind of things.
> 
> So what about getting ride of config.minifyCSS and config.compressCss
> ... or config.minifyCss and config.compressCSS ?

We should use lowerCamelCase like we to for PHP functions:
config.minifyCss
config.compressCss

While we are it, we should check how much performance gets eaten if we just 
convert all keys to lower case at the time of parsing. I do not know if this 
even works or if this would effect the rendering of values, but we should 
have a look at it.
I am not aware of keys that exists in that would conflict with each other if 
we ignore the case.

What do you think about it?

Cheers
-- 
Philipp Gampe – PGP-Key 0AD96065 – TYPO3 UG Bonn/Köln
Documentation – linkvalidator
TYPO3 .... inspiring people to share!