A collection of helpers for handlebars (rust) to manage string, json, yaml, toml, path, file, http request.

Helpers extend the template to generate or to transform content. Few helpers are included, but if you need more helpers, ask via an issue or a PR.

To use an helper:

// arguments are space separated
{{ helper_name arguments}}

To chain helpers, use parenthesis:

{{ to_upper_case (to_singular "Hello foo-bars") }}
// -> BAR

{{ first_non_empty (unquote (json_str_query "package.edition" (read_to_str "Cargo.toml") format="toml")) (env_var "MY_VERSION") "foo" }}
// -> 2018

see Handlebars templating language

To not "import" useless dependencies, use crate's features:

[features]
default = [ "string", "http", "json", "jsonnet" ]
string = [ "Inflector", "enquote" ]
http = [ "attohttpc" ]
json = [ "lazy_static", "serde", "serde_json", "serde-transcode", "serde_yaml", "toml" ]
jsonnet = [ "jsonnet-rs" ]

• String transformation
• Http content
• Path extraction
• File
• Environment variable
• JSON & YAML & TOML
  • Helpers
  • Blocks
  • Edition via jsonnet
• Assign

Helper able to render body response from an http request.

Helper able to extract (or transform) path (defined as string).

for the same input: "/hello/bar/foo.txt"

Helper to read file content.

Helper able to get environment variables.

Specials environment variables are predefined (some of them come from std::env::consts - Rust):

• json_query query:String data:Json: Helper able to extract information from json using JMESPath syntax for query.
• json_str_query query:String data:String: Helper able to extract information from json using JMESPath syntax for query, data follows the requested format.
• json_to_str data:Json: convert a json data into a string following the requested format.
• str_to_json data:String: convert(parse) a string into a json following the requested format.

The optional requested format, is the format of the string with data:

• "json" (default if omitted)
• "json_pretty" json with indentation,...
• "yaml"
• "toml"
• "toml_pretty"

{{#from_json format="toml"}}
{"foo": {"hello":"1.2.3", "bar":{"baz":true} } }
{{/from_json}}

[foo]
hello = "1.2.3"
[foo.bar]
baz = true

{{#to_json format="toml"}}
[foo]
bar = { baz = true }
hello = "1.2.3"
{{/to_json}}

{
  "foo": {
    "bar": {
      "baz": true
    },
    "hello": "1.2.3"
  }
}

{{#from_json format="toml"}}
{"foo":{"bar":{"baz":true}}}
{{/from_json}}

foo:
  bar:
    baz: true

{{#to_json format="yaml"}}
foo:
    bar:
        baz: true
{{/to_json}}

{
  "foo": {
    "bar": {
      "baz": true
    }
  }
}

Note: YAML & TOML content are used as input and output format for json data. So capabilities are limited to what json support (eg. no date-time type like in TOML).

For more advanced edition of json, you can use jsonnet.

A data templating language for app and tool developers

• See the doc of jsonnet for more samples, syntax info,...
• This block can be combined with conversion helper/block for YAML & TOML to provide edition capabilities for those format
• the output should a valid json, except if string_output = false is set as parameter of the block.

{{#jsonnet}}
local v = {"foo":{"bar":{"baz":false}}};
v {
  "foo" +: {
      "bar" +: {
          "baz2": true
      }
  }
}
{{/jsonnet}}

{
  "foo": {
      "bar": {
          "baz": false,
          "baz2": true
      }
  }
}

Helper able to assign (to set) a variable to use later in the template.