Skip to end of metadata
Go to start of metadata
Icon

This is only available in Confluence 4.0+.

This page describes how you can write a Soy template in your plugin to use in JavaScript. This can be useful when generating a dialog or some piece of content to display on the page.

References

Quick Guide

1. Create a soy file

Under the plugins resource directory, create a soy file. Each soy file needs to have a namespace declaration at the top of the file. It must be declared before any templates are declared. You can think of the namespace as a javascript namespace equivalent. You can put it under your plugin's namespace or use the existing Confluence.Templates​.

2. Write your template

Next comes your actual template declaration, which is simply declared with {template .templateName}. If your template needs parameters, you must declare them in the 'javadoc' part before your template. You can then use the param in the template with a {$paramName} syntax. Here is a simple example soy file:

example.soy

3. Add your template to a web-resource

Since a soy file gets transformed in a js file, we need to declare it with all the other js files in a <web-resource> element of a plugin xml. You will also need to copy the soy transformer config into the <web-resource> element. Here is an example:

4. Use the template in your javascript

You can now invoke the template by simply calling a javascript function with your previously declared namespace. In this example it would be something like:

i18n in your templates

You will often need to use i18n in your templates. To do so, simply use the {getText('key')} syntax.

Icon

GOTCHA: You must use single quotes for string literals in soy. Double quotes are for html attribute values.

Here is an example template using i18n.

Calling another template from a template

You may want to reuse an existing template from another template. To do this you can simply use the call command to invoke another template. You can optionally pass in all the params from one template to another or configure individual parameters that get passed through. Here is an example with a single parameter being passed through.

  • No labels

1 Comment

  1. /*  A template for a dialog help link * @param href key of the doc link url */

    Unknown macro: {template .helpLink}

    <divclass="dialog-help-link"><a href="{$href}" target="_blank">

    Unknown macro: {getText('help.name')}

    </a></div>

    Unknown macro: {/template}