Use

canViewCallbacks.tag is a low-level way to add custom behavior to custom elements. Often, you want to do this with can-component. However, callbacks.tag is useful for when can-component might be considered overkill. For example, the following creates a jQueryUI DatePicker every time a <jqui-datepicker> element is found:

callbacks.tag( "jqui-datepicker", function( el, tagData ) {
    $( el ).datepicker();
} );

The tagHandler’s tagData argument is an object that contains the stache Scope and helper [can-view-scope.Options] where el is found and a [can-stache.renderer sub-template] that renders the contents of the template within the custom tag.

Getting values from the template

tagData.scope can be used to read data from the template. For example, if I wanted the value of "format" within the current template, it could be read like:

callbacks.tag( "jqui-datepicker", function( el, tagData ) {
    $( el ).datepicker( { format: tagData.scope.get( "format" ) } );
} );

const template = mustache( "<jqui-datepicker></jqui-datepicker>" );
template( { format: "mm/dd/yy" } );

tagData.options contains the helpers and partials provided to the template. A helper function might need to be called to get the current value of format like:

callbacks.tag( "jqui-datepicker", function( el, tagData ) {
    $( el ).datepicker( {
        format: tagData.options.get( "helpers.format" )()
    } );
} );

const template = mustache( "<jqui-datepicker></jqui-datepicker>" );
template( {}, { format: function() {
    return "mm/dd/yy";
} } );

Responding to changing data

Often, data passed to a template is observable. If you use tag, you must listen and respond to changes yourself. Consider if format is property on a settings can-map like:

const settings = new Map( {
    format: "mm/dd/yy"
} );

You want to update the datepicker if format changes. The easiest way to do this is to use Scope’s compute method which returns a get-set compute that is tied to a key value:

callbacks.tag( "jqui-datepicker", function( el, tagData ) {

    const formatCompute = tagData.scope.compute( "format" );
    const changeHandler = function( ev, newVal ) {
        $( el ).datepicker( "option", "format", newVal );
    };

    formatCompute.bind( "change", changeHandler );

    changeHandler( {}, formatCompute() );

    // ...

} );

const template = mustache( "<jqui-datepicker/>" );
template( settings );

If you listen on something outside the tag, it’s a good practice to stop listening when the element is removed from the page:

domEvents.addEventListener.call( el, "removed", function onremove() {
    compute.off( "change", showOrHide );
    formatCompute.unbind( "change", changeHandler );
} );

Subtemplate

If content is found within a custom tag like:

const template = stache( `
  <my-form>
     <input value="{{first}}"/>
     <input value="{{last}}"/>
   </my-form>
` );

A separate template function is compiled and passed as tagData.subtemplate. That sub-template can be rendered with custom data and options. For example:

callbacks.tag( "my-form", function( el, tagData ) {
    const frag = tagData.subtemplate( {
        first: "Justin"
    }, tagData.options );

    $( el ).html( frag );
} );

template( {
    last: "Meyer"
} );

In this case, the sub-template will not get a value for last. To include the original data in the sub-template’s scope, add to the old scope like:

callbacks.tag( "my-form", function( el, tagData ) {
    const frag = tagData.subtemplate(
        tagData.scope.add( { first: "Justin" } ),
        tagData.options
    );

    $( el ).html( frag );
} );

template( {
    last: "Meyer"
} );