We have moved to GitHub Issues
Created by Jan Skovgaard 16 Sep 2012, 12:20:36 Updated by Sebastiaan Janssen 11 Oct 2014, 11:32:27
I don't see any reason why this setting is configurable. If someone turns it off they're doomed to have a lot of problems if they use special chars etc. - I can't make up a scenario where you'll want to do this - smells like a lot of trouble so I suggest removing the option completely.
I disagree. I always turn this setting off, and never have had problems because I know not to use special chars in property names (which are essentially variable names). Content Editors shouldn't be creating doctype properties, so as long as your developers know, it isn't a problem.
That being said, the reason I always turn it off is because it forced lower case on the first letter of property names. Call me crazy, but I'm partial to UpperCamelCasing. In my opinion, it looks nicer, and is a MS/.Net standard. I'd say that you can remove this setting if you also remove the case-formatting from the back-office validation routine.
EDIT: Nevermind - I now see from a quick test that in v7 the cursed lowercase is already removed :-) So my comment is only applicable to previous versions. Thanks, team!
In any case, the setting is no longer in the config file for a while in v7 now. :)
Difficulty: Very Easy
Backwards Compatible: True
Due in version: