Templates
Your Wire's HTML. Simple as that. Honestly.
Wires require a template that contains the HTML to be rendered.
By default, Templates exist within your project under ./views/wires/[templateName].cfm
. You can override the default template location with the configuration setting templatesLocation.
See Configuration
Implicit Path
If you haven't specified your template file name inside your Wire using template, a template will be implicitly loaded based on the Wire's file name.
For the example above, the template ./views/wires/tasklist.cfm
will be rendered.
File names should be lowercase when using Implicit Lookups. This is to avoid issues on case-sensitive file systems.
Explicit Path
You can specify the path to your Template using template
.
In CBWIRE 1.x, you would define the template path using view
but this has been deprecated and template
should be used going forward.
onRender
Instead of creating a .cfm template, you can define an onRender() method on your Wire.
See the Wire Lifecycle page for additional details.
Prevent Rendering
Within your Actions, you can call the method noRender()
to prevent your template from re-rendering. This can reduce the returned payload size for actions that do not change the UI.
Outer Element
Be sure your template includes a single outer element such as<div>
.
If an outer element is not detected, an OuterElementNotFoundexception is thrown.
You can use something other than <div></div>.
Last updated