Skip to main content

Handlebars syntax

Tom Santiago
  • Updated
Follow

Functional implementation heavily relies on proper use of handlebars curly braces.

Typographical Conventions

Item Description 
{{ }}
 Handlebars double-braces will URL encode characters that are able to be URL encoded. The double-braces themselves do not display in output (escaped). 
{{{ }}}
 Handlebars triple-braces remove URL encoding from characters that already have URL encoding applied. Triple-braces will also display in the output (unescaped). 
{{{{ }}}}
 Handlebars raw block. 
{{name}}
 Handlebars expression. 
{{first.name}}
 Dot-notation for nested objects. 
\{{escaped}}
 Using a backslash as a leading character before an expression
prints the entire {{expression}} to output (with braces).		 
Template
 The handlebars expressions and/or helpers chained in a block or
sequence.		 
Context
 JavaScript Object Notation (JSON ) files are referred to as "Context" when using Handlebars. These are the files that you upload in integrator.io or sample data used to render outputs for testing for your JSON files. 
Output
 Shows the formatted output.

Code that appears between the curly braces {{field}} are known as “expressions” in Handlebars. Handlebars expressions may be used for:

  • Mapping Export and Import application fields;
  • Performing dynamic arithmetic calculations on the values being exported;
  • Performing dynamic encoding and decoding of data during integration.

Handlebars expressions use dot-notation to access object properties. The expression in the following example is set to look up the value in the “title” field name within the “library” object or parent property.

Template Context Output 
{{library.title}}
 
{
    "library": {
        "album": "The Sound",
        "title": "Danube Incident",
        "artist": "Lalo Schifrin"
    }
}
 
Danube Incident

Related articles

Comments

0 comments

Please sign in to leave a comment.