Specify template engine or parser

Specify the data parser

-r, --parser: Defines the parser to use when the source data is provided through the console. Accepted values are yaml, json, xml, url, FrontMatter or FrontMatterMarkdown. This option is required only when the --source argument is omitted or if the extension of the source file is not recognized to determine the parser. For multiple sources, this option applies to all files, regardless of their extensions or any pre-assigned engine associations.

didot -t template.hbs -s data.txt -r json -o output.txt

In this example:

-X, --parser-extension: Defines the association of a file’s extension with a parser. More than one association can be specified.

didot -t template.txt -s data.json -X dat:Json;fm:FrontMatter -o output.txt

In this example:

template.txt is the template file.
data.json is the data JSON file.
dat:Json;fm:FrontMatter is associating JSON to the extension .dat and FrontMatter to the extension .fm.
output.txt is the file where the output will be rendered.

By default following file’s extension association are registered:

-e, --engine: Defines the template engine to use independantly of the template file extension. Accepted values are scriban, dotliquid, fluid, handlebars, stringtemplate, smartformat.

didot -t template.txt -s data.json -e handlebars -o output.txt

In this example:

-x, --engine-extension: Defines the association of a file’s extension with a template engine. More than one can be specified.

didot -t template.txt -s data.json -x txt:handlebars;liquid:fluid -o output.txt

In this example:

template.txt is the template file.
data.json is the data JSON file.
txt:handlebars;liquid:fluid is associating Handlbars to the extension .txt and Fluid to the extension .liquid.
output.txt is the file where the output will be rendered.

By default following file’s extension association are registered: