Return the debug info about this component.
Disable the component. Normally this means that the component will not execute handlers for the framework events (query events, for example). Components are enabled by default on creation.
Enable the component. Normally this means that the component will execute handlers for the framework events (query events, for example). Components are enabled by default on creation.
Return the bindings, or environment, for the current component.
Get the bound component to the given HTMLElement. Throws an assert if the HTMLElement has no component bound, unless using the noThrow argument.
If there is multiple component bound to the current HTMLElement, you must specify the component class.
HTMLElement for which to get the bound component.
Optional component class. If the HTMLElement has multiple components bound, you must specify which one you are targeting.
Boolean option to tell the method to not throw on error.
Allows the component to bind events and execute them only when it is enabled.
Contains the state of options for different components. Mainly used by ResultLink.
Contains the state of different components (enabled vs disabled). Allows to get/set values. Triggers component state event when modified. Each component can listen to those events.
A disabled component will not participate in the query, or listen to ComponentEvents.
Allows component to log in the dev console.
Contains the singleton that allows to trigger queries.
Contains the state of the query. Allows to get/set values. Trigger query state event when modified. Each component can listen to those events.
A reference to the root HTMLElement (the SearchInterface).
A reference to the root of every component, the SearchInterface.
The static ID that each component needs in order to be identified.
For example, SearchButton -> static ID: SearchButton -> className: CoveoSearchButton
A reference to the Analytics.client.
Specifies the boolean condition that the result must satisfy in order for the template to load.
Example:
data-condition='percentScore > 80'
data-condition='foo'
Specifies how to find the template. This can be either a CSS selector or an HTML id
attribute.
Examples:
data-template-selector='.MySelector'
id
: data-template-id='MyId'
Creates a new TemplateLoader.
The HTMLElement on which to instantiate the component.
The options for the TemplateLoader component.
The bindings that the component requires to function normally. If not set, these will be automatically resolved (with a slower execution time).
The result to associate the component with.
The TemplateLoader component can load one result template into another. You should normally declare any reusable result template outside of the ResultList component. Otherwise, the framework will evaluate the
data-condition
of the reusable result template and possibly render it.Example:
[ ... ] <!-- A reusable result template. Note that it is important to declare it outside of the ResultList component. --> <script type='text/underscore' class='result-template' id='ReusableTemplate'> <table class='CoveoFieldTable'> <tr data-field='@source' data-caption='Source'></tr> <tr data-field='@percentScore' data-caption='Score'></tr> </table> </script> [ ... ] <div class="CoveoResultList" data-wait-animation="fade" data-auto-select-fields-to-include="true"> <!-- A custom result template for Lithium messages. --> <script type='text/underscore' class='result-template' data-condition='raw.filetype == "lithiummessage"'> <div> <img class='CoveoIcon' data-small='true'> <a class='CoveoResultLink'></a> <div class='CoveoTemplateLoader' data-template-id='ReusableTemplate'></div> </div> </script> <!-- A custom result template for images. --> <script type='text/underscore' class='result-template' data-condition='raw.filetype == "Image"'> <div> <img class='CoveoIcon' data-small='true'></img> <a class='CoveoResultLink'> <img class='CoveoThumbnail'> </a> <div class='CoveoTemplateLoader' data-template-id='ReusableTemplate'></div> </div> </script> </div> [ ... ]
See Result Templates.