Home
Bernd Ebertz edited this page Jul 4, 2021
·
14 revisions
While template engines, that are based on scripting languages, often lead to templates, overwhelmingly filled with all types of logic, Snippetory rather acts as a next generation token replacer.
- By regions it supports loops and conditional inclusion
- metadata describes how data is bound to the template.
- intact templates makes code generation more efficient. By using the right Syntax it's possible to create have re-factoring support and other goodies on your templates.
- Encodings make sure the output is sane.
- Formats ease the binding of different datatypes and formatting according to the locale.
- TemplateWrapper allow implementation of crosscutting concerns
- The sql module provides named parameters to JDBC no matter it's for
- Mysql
- SQL Server
- Oracle
- or any other JDBC database
- The Groovy module provides
- a TemplateBuilder
- and a TemplateDynamizer to make the usage of Snippetory in pretty transparent