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 default filters which all end users can apply.
End users cannot modify or delete these filters. These filters do not count as "user-made" filters, but rather as "built-in" filters created by the developer of the search page.
Note:
You cannot set this option directly in the component markup as an HTML attribute. You must either set it in the
init
call of your search interface (see Passing Component Options in the init Call), or before theinit
call, using theoptions
top-level function (see Passing Component Options Before the init Call).
Filters should follow this definition:
filters : { [caption : string] : { expression : string, tab? : string[] } }
;
Example:
var myFilters = { "Only Google Drive Items" : { expression : "@connectortype == 'GoogleDriveCrawler'", tab : ["Tab1", "Tab2"] },
"Another Filter" : { expression : [ ... another expression ... ] },
[ ... ] };
// You can set the option in the 'init' call:
Coveo.init(document.querySelector("#search"), {
ResultsFiltersPreferences : {
filters : myFilters
}
});
// Or before the 'init' call, using the 'options' top-level function:
// Coveo.options(document.querySelector("#search"), {
// ResultsFiltersPreferences : {
filters : myFilters
}
// });
Default value is undefined
.
data-include-in-breadcrumb='true' data-include-in-breadcrumb='false'
Specifies whether to show the Create button that allows the end user to create filters.
If you set this option to false
, only the pre-populated
filters
are available to the end user.
Default value is true
.
data-show-advanced-filters='true' data-show-advanced-filters='false'
Creates a new ResultsFiltersPreferences
component.
The HTMLElement on which to instantiate the component.
The options for the ResultsFiltersPreferences
component.
The bindings that the component requires to function normally. If not set, these will be automatically resolved (with a slower execution time).
The
ResultFiltersPreferences
component allows end users to create custom filters to apply to queries. These filters are saved to local storage.Only advanced end users who understand the Coveo query syntax should use this feature (see Coveo Query Syntax Reference).
This component is normally accessible through the
Settings
menu. Its usual location in the DOM is inside thePreferencesPanel
element.See also the ResultsPreferences component.