FM2 traditionally uses a weird naming convention, where directive names are all-lower-case (like #elseif), and other names use snake case (like ?upper_case or date_format). For a while it also supports camel case (you just use it in the template, like ?upperCase, #elseIf, etc., and it switches to that mode automatically).
I belive camel case is the clear winner, because the names in the data-model are almost always also use that, since in the Java world that's the norm (also in the JavaScript world BTW). I propose that FM3 should only support the camel case variation. (Note that this only affect the names defined by FreeMarker, not the names coming from the data-model.) That yet again simplifies tooling too. Any thoughts? -- Thanks, Daniel Dekany
