Extend Knot.x Templating Engine by custom tags processing

[malaskowski]

Custom tags will be placed inside snippet and should be interpreted by Knot.x Templating Engine after Handlebars processing. Inside custom tags developer will put JSON object that describes tag configuration. Custom <knotx> tags should never be rendered in the final page.

Example of custom tags:

  <script data-api-type="templating" 
      data-uri="/service/mock/second.json"
      type="text/x-handlebars-template">
    <knotx:customTag>
      {
        some options...
      }
    </knotx:customTag>
    <h2>Snippet2 - {{message}}</h2>
    <p>Snippet2 - {{body.a}}</p>
    {{#string_equals status "success"}}<p>Success!</p>{{/string_equals}}
  </script>

[tomaszmichalak]

One script tag can contain many different knotx custom tags. One script tag can contain at most one particular knotx custom tag.

What do you think about that implementation simplification?

[marcinczeczko]

Closing as we will go towards different approach