Re: [freemarker-cli] Naming of Tools and DataSources in FreeMarker Data Model

2020-07-09 Thread Daniel Dekany
Of course we should use the same convention everywhere. Choosing the sane variant of camel case (i.e., yaml, and not YAML) is a pretty obvious choice. Also, it's freemarker in that convention, not freeMarker, since it's one word. (Yeah, it's quite a bad product name for a few reasons... but we

Re: [freemarker-cli] Naming of Tools and DataSources in FreeMarker Data Model

2020-07-08 Thread Siegfried Goeschl
Hi Daniel, Aligned the naming but for the tools it is probably over the top ... We currently have - csv - dataframe - excel - exec - freemarker - grok - gson - jsonpath - jsoup - properties - system - uuid - xml - yaml Which would change

Re: [freemarker-cli] Naming of Tools and DataSources in FreeMarker Data Model

2020-07-08 Thread Daniel Dekany
As in plain English it's rather "data source" than "datasource", thus the variable name should stay "dataSource". Whether one aesthetically likes it or not, that's the convention in Java circles. For same reason it should be tools.dataFrame (instead of tools.dataframe), and dataSource.mimeType

[freemarker-cli] Naming of Tools and DataSources in FreeMarker Data Model

2020-07-07 Thread Siegfried Goeschl
HI folks, I'm using now a map for the tools, e.g. FreeMarker CLI Tools -- <#list tools?keys?sort as name> - ${name?right_pad(20)} : ${tools[name]} FreeMarker CLI Tools