As designed Template modification key validation should be case insensitive

MilkyMeda

Active member
Affected version
2.2.3 Patch 1
Case sensitivity is dangerous for development output because the filesystem doesn't allow files to be samely named but differently cased. This results in overriding the previous modification file depending on which one of them just changed.
 
This simply isn't something that will be changed. You'll note that virtually all of our identifiers in this style are case sensitive (phrases, templates, etc). Case insensitivity causes different issues, including scenarios that cause issues in normal usage of the software (due to situations that would attempt to mix case sensitive and insensitive scenarios). Use of case sensitive identifiers avoids these issues.

We don't recommend that you use identifiers that differ only by case if you are using development output. However, there is nothing to strictly stop you from doing that if you use a case sensitive filesystem. The property you refer to isn't universal; notably Linux FSes tend to be case sensitive, while Mac and Windows aren't.
 
Top Bottom