Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →

doofinder

Package Overview

Dependencies

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

doofinder

Javascript Library for Doofinder Search API

0.10.0
Source
npm

Version published: 9 years ago

Weekly downloads: 88; decreased by-32.82%

Maintainers: 1

Weekly downloads

Created: 9 years ago

Source

jsDoofinder (In progress)

This library allows you to make requests to Doofinder Search Engines and show the results in your website. You'll be able to retrieve and shape your data easily with it.

Summary

Installation

npm

npm install doofinder

bower

bower install doofinder

Downloadable minified javascript file

https://raw.githubusercontent.com/doofinder/js-doofinder/master/dist/doofinder.min.js

CSS

We offer some simple CSS. You can download it in the link https://raw.githubusercontent.com/doofinder/js-doofinder/master/dist/doofinder.css

Quick Start

In this example we'll write a view that will just show results.

Let's begin by showing a simple HTML template (myview.html):

<html lang="en">
<head>
<script type="application/javascript" src="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js"></script>
<script type="application/javascript" src="path/to/your/js/doofinder.min.js"></script>
<script>
(function(doofinder, document){
  $(document).ready(function(){
    // Use here your Search Engine hashid and doofinder zone
    var client = new doofinder.Client('97be6c1016163d7e9bceedb5d9bbc032', 'eu1');
    // #query is the DOM selector that points to the search box
    var queryInputWidget = new doofinder.widgets.QueryInput('#query');
    // #scroll is where we'll display the results
    var resultsWidget = new doofinder.widgets.ScrollResults('#scroll');
    // The controller to rule them all
    var controller = new doofinder.Controller(
        client,
        [queryInputWidget, resultsWidget]
    );
  });
})(doofinder, document);
</script>
<style>
#scroll{
    position: relative;
    height: 800px;
    overflow: auto;
}
</style>
</head>
<body>
  <input type="text" id="query"/>
  <div id="scroll">
  </div>
</body>

Note that we are importing two javascript files:

jquery.min.js: we use it to make sure that everything is being done when the document is ready.
doofinder.min.js: contains doofinder namespace with its classes.

We need to create the inner scroll via css.

The options we have filled in for the Client:

hashid: the unique hashid of your search engine.
zone: the zone where your search engine is located (eu1, us1, ...).

For the QueryInput widget:

queryInput selector: the CSS selector of our query input.

For the ScrollResults widget:

scroll selector: the CSS selector for the scroll wrapper.

WARNING: Note that Doofinder Search API is protected with CORS, so you must enable the host you are requesting from. You can do this from your Doofinder Administration Panel > Configuration > TODO(@ecoslado) This feature in Admin Panel.

With all this in place you'll have a search box where you can write a query and the results will be shown. Scrolling into the layer you'll see more results.

Classes

Controller

Controller is the class that manages client and widgets. Allows you to make different queries to your index and interact with the different widgets you will instantiate.

constructor

Argument	Required	Type	Description
client	Yes	`doofinder.Client`	The Search API wrapper
widgets	Yes	`doofinder.Widget` `Array(doofinder.Widget)`	Array of widgets for interacting and rendering the results
searchParameters	No	`Object`	An object with params that will passed to the client for every search. You can use here all the parameters defined in Doofinder Search API.

search

This method makes a query to the Search API and renders the results into the widgets.

Argument	Required	Type	Description
query	Yes	`String`	The query terms.
params	No	`Object`	An object with search parameters. You can use here all the parameters defined in Doofinder Search API.

Asks for the next page of the previous search done, and sends the response to all widgets to render it.

getPage

Asks for a concrete page. Then pass the response to all widgets to render it.

Argument	Required	Type	Description
page	Yes	`Number`	The page requested

addFilter

Adds a filter to the currently applied in the search.

Argument	Required	Type	Description
facet	Yes	`String`	The name of the facet.
value	Yes	`String` `Object`	The value the facet should have. This can be a `String`, if the facet is a term facet or an `Object` if it's a range.

removeFilter

Removes a filter from the currently applied.

Argument	Required	Type	Description
facet	Yes	`String`	The name of the facet.
value	Yes	`String` `Object`	The value of the facet. This can be a `String`, if the facet is a term facet or an `Object` if it's a range.

refresh

Makes a search with the current filter status. Then, it calls to every widget to render the results.

addWidget

Adds a widget to the controller after the instantiation.

Argument	Required	Type	Description
widget	Yes	`doofinder.Widget`	The widget to add.

bind

This method adds a callback to an event triggered from the controller. Events are triggered from the controller when a query is going to be done or when results are received.

Argument	Required	Type	Description
event	Yes	`String`	The query terms.
callback	Yes	`Function`	The function which receives the API Search response.

The events you can bind in widget are the described above. Note that each event sends different arguments to the callback in order to implement it properly.

Event Name	Callback Arguments	Description
df:search	event`Object`: object with the event information. params`Object`: the object will be send as params to the Search API.	This event is triggered when controller.search is called.
df:next_page	event`Object`: object with the event information. params`Object`: the object will be send as params to the Search API.	This event is triggered when controller.nextPage is called.
df:get_page	event`Object`: object with the event information. params`Object`: the object will be send as params to the Search API.	This event is triggered when controller.getPage is called.
df:results_received	event`Object`: object with the event information. res`Object`: the Search API response	This event is triggered when new results are received from Search API.

hit

Sends a request to the Search API in order to account the hits for a product.

Argument	Required	Type	Description
dfid	Yes	`String`	Unique product identifier.

Widgets are visual elements that take part into the search. They can be search inputs, places where display the results, places to put the facets, etc. The events you can bind in widget depend on the widget you are instantiating. Above we'll describe all the available widget and theirs correponding events.

widgets.QueryInput

This widget triggers searches when a user types on it.

constructor

Argument	Required	Type	Description
selector	Yes	`String`	Input CSS selector.
options	No	`Object`	Options to configure the input.

The options to configure the input are:

Option	Type	Description
wait	`Number`	milliseconds that the widget waits to check the input content length.
captureLength	`Number`	number of Requireds typed when first search is performed

bind

This method adds a callback to an event triggered from the widget. Events are triggered from every widget when a query is going to be done or when results are received or when they are rendered in a widget.

Argument	Required	Type	Description
event	Yes	`String`	The query terms.
callback	Yes	`Function`	The function which receives the API Search response.

widgets.Results

This widget shows the results in a DOM node. When a new search or filter is done or a new page is requested the new content will replace the older.

constructor

Argument	Required	Type	Description
container	Yes	`String`	Results container CSS selector.
options	No	`Object`	Options to configure the input.

The options to configure the widget are:

Option	Type	Description
template	`String`	Handlebars template to shape the results.
templateVars	`Object`	Extra info you want to render in the template. Look at Example 2.
templateFunctions	`Object`	Custom helpers to use in your template. Look at Example 3.

bind

Argument	Required	Type	Description
event	Yes	`String`	The query terms.
callback	Yes	`Function`	The function which receives the API Search response.

The events you can bind in widget are the described above. Note that each event sends different arguments to the callback in order to implement it properly.

Event Name	Callback Arguments	Description
df:rendered	event`Object`: object with the event information. res`Object`: Doofinder Search API response.	This event is triggered when the results are rendered.

widgets.ScrollResults

This widget render the results in an DOM node with an inner scroll. So the next page will be requested when scroll reaches the bottom.

constructor

Argument	Required	Type	Description
container	Yes	`String`	Results container CSS selector.
options	No	`Object`	Options to configure the input.

The options to configure the widget are:

Option	Type	Description
template	`String`	Handlebars template to shape the results.
templateVars	`Object`	Extra info you want to render in the template. Look at Example 2.
templateFunctions	`Object`	Custom helpers to use in your template. Look at Example 3.
scrollOffset	`Number`	Distance in pixels to the bottom in scroll when next page is requested. Default 50.

There is some CSS you have to add to your container in order to make the inner scroll to work properly:

#container {
  height: 800px;
  position: relative;
  overflow: auto;
}

In the example above #container could be your scroll container selector and the height can be set to the value you prefer.

bind

Argument	Required	Type	Description
event	Yes	`String`	The query terms.
callback	Yes	`Function`	The function which receives the API Search response.

The events you can bind in widget are the described above. Note that each event sends different arguments to the callback in order to implement it properly.

Event Name	Callback Arguments	Description
df:rendered	event`Object`: object with the event information. res`Object`: Doofinder Search API response.	This event is triggered when the results are rendered.
df:hit	event`Object`: object with the event information. dfid`String`: Doofinder Item Identifier. Useful to make the controller.hit call. url`String`: The url associated to the item. Useful to make the controller.sendToGA call.	This event is triggered when a result link is clicked.

widgets.TermFacet

This widget render a term facet in a list of terms.

constructor

Argument	Required	Type	Description
container	Yes	`String`	Results container CSS selector.
name	Yes	`String`	The facet key.
options	No	`Object`	Options to configure the input.

The options to configure the widget are:

Option	Type	Description
template	`String`	Handlebars template to shape the results.
templateVars	`Object`	Extra info you want to render in the template. Look at Example 2.
templateFunctions	`Object`	Custom helpers to use in your template. Look at Example 3.

bind

Argument	Required	Type	Description
event	Yes	`String`	The query terms.
callback	Yes	`Function`	The function which receives the API Search response.

The events you can bind in widget are the described above. Note that each event sends different arguments to the callback in order to implement it properly.

Event Name	Callback Arguments	Description
df:rendered	event`Object`: object with the event information. res`Object`: Doofinder Search API response.	This event is triggered when the facet is rendered.

widgets.RangeFacet

This widget render a range facet in a slider. To show it properly is necessary some CSS. You can add this stylesheet:

https://raw.githubusercontent.com/doofinder/js-doofinder/master/dist/doofinder.css

constructor

Argument	Required	Type	Description
container	Yes	`String`	Results container CSS selector.
name	Yes	`String`	The facet key.
options	No	`Object`	Options to configure the input.

The options to configure the widget are:

Option	Type	Description
template	`String`	Handlebars template to shape the results.
templateVars	`Object`	Extra info you want to render in the template. Look at Example 2.
templateFunctions	`Object`	Custom helpers to use in your template. Look at Example 3.

bind

Argument	Required	Type	Description
event	Yes	`String`	The query terms.
callback	Yes	`Function`	The function which receives the API Search response.

The events you can bind in widget are the described above. Note that each event sends different arguments to the callback in order to implement it properly.

Event Name	Callback Arguments	Description
df:rendered	event`Object`: object with the event information. res`Object`: Doofinder Search API response.	This event is triggered when the facet is rendered.

Client

constructor

Argument	Required	Type	Description
hashid	Yes	`String`	The unique search engine identifier.
API Key	Yes	`String`	The secret key to authenticate the request.
types	No	`Array`	An array of datatypes to restrict the queries to them.

search

This method performs a Search API call and retrieves the data. The data will be received by a callback function.

Argument	Required	Type	Description
query	Yes	`String`	The query terms.
params	No	`Object`	The query terms.
callback	Yes	`Function`	The function which receives the API Search response.

Examples

Example 1: Create a simple template to show results.

In the Quick Start example we composed a simple view using the Doofinder Library. Let's see how to shape the results by a Handlebars template.

 
var resultsTemplate = '{{#each results}}' +
  ' <div>'+
  '   <div>' +
  '     <a href="{{href}}">'+
  '       <img src="{{image}}" alt="{{header}}">'+
  '     </a>'+
  '     <div>'+
  '       <a target="_blank" data-df-hitcounter="{{dfid}}" href="{{href}}">'+
  '         <div>{{header}}</div>' +
  '         <div>{{body}}</div>' +
  '         <div>' +
  '          <span>{{#format-currency}}{{price}}{{/format-currency}}</span>' +
  '         </div>'+
  '       </a>' +
  '    </div>' +
  '  </div>' +
  '</div>' +
  '{{/each}}';

var resultsWidget = new doofinder.widgets.ScrollResults('#scroll', {template: resultsTemplate});

Let's have a look to the template:

We used {{#each results}} as a loop where we iterated through the items.
We used {{field_name}} tags to print the content of a field.
We used {{#if filed_name}} to check the presence of a field.
We used {{#format-currency}} helper to print the price with the coin symbol and formatted.
Note that we use a data attribute to show the dfid. You can use this to send it with the Controller.hit method.

Example 2: Adding extra info to our template.

Maybe you want to add more information to your template dynamically. Imagine you want to show prices lower that a given number, i.e. 100. You can add this variable to the template scope by the option templateVars.

var resultsWidget = new doofinder.widgets.ScrollResults('#scroll', {
  template: resultsTemplate,
  templateVars: {
    maxPrice: 100
    }
  });

So you can modify your template in order to show just the prices lower than maxPrice.

 
var resultsTemplate = '{{#each results}}' +
  ' <div>'+
  '   <div>' +
  '     <a href="{{href}}">'+
  '       <img src="{{image}}" alt="{{header}}">'+
  '     </a>'+
  '     <div>'+
  '       <a target="_blank" data-df-hitcounter="{{dfid}}" href="{{href}}">'+
  '         <div>{{header}}</div>' +
  '         <div>{{body}}</div>' +
  '         {{#lt price ../maxPrice}}'
  '         <div>' +
  '          <span>{{#format-currency}}{{price}}{{/format-currency}}</span>' +
  '         </div>' +
  '         {{/lt}}' +
  '       </a>' +
  '    </div>' +
  '  </div>' +
  '</div>' +
  '{{/each}}';

var resultsWidget = new doofinder.widgets.ScrollResults('#scroll', {
  template: resultsTemplate,
  templateVars: {
    maxPrice: 100
    }
  });

And we have used the {{#lt}} helper to compare the price with the maxPrice. Note that we have written ../maxPrice instead of maxPrice. This is because we are in the loop and we must access to a variable out of results array. For more information about Handlebars templates, click here.

Example 3: Create a custom template function.

Template functions are called helpers in Handlebars. You can create and add custom helpers to your template by using the templateFunctions option. We'll create a helper that convert a text in bold.


{
  templateFunctions: {
    bold: function(options){
      return "<b>" + options.fn(this) + "</b>"
    }
}

This helper will take the text in the tag and will wrapper it with the <b> tag. Note that options.fn(this) returns the text wrapped by the helper.

We'll use the helper for showing the header and instantiate the widget.

var resultsTemplate = '{{#each results}}' +
  ' <div>'+
  '   <div>' +
  '     <a href="{{href}}">'+
  '       <img src="{{image}}" alt="{{header}}">'+
  '     </a>'+
  '     <div>'+
  '       <a target="_blank" data-df-hitcounter="{{dfid}}" href="{{href}}">'+
  '         <div>{{#bold}}{{header}}{{/bold}}</div>' +
  '         <div>{{body}}</div>' +
  '         <div>' +
  '          <span>{{#format-currency}}{{price}}{{/format-currency}}</span>' +
  '         </div>'+
  '       </a>' +
  '    </div>' +
  '  </div>' +
  '</div>' +
  '{{/each}}';

var resultsWidget = new doofinder.widgets.ScrollResults('#scroll', {
  template: resultsTemplate,
  templateFunctions: {
    bold: function(options){
        return "<b>" + options.fn(this) + "</b>"
      }
    }
  });

Keywords

doofinder

FAQs

What is doofinder?

Is doofinder popular?

Is doofinder well maintained?

Package last updated on 21 Dec 2015

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

doofinder

jsDoofinder (In progress)

Summary

Installation

npm

bower

Downloadable minified javascript file

CSS

Quick Start

Classes

Controller

constructor

search

nextPage

getPage

addFilter

removeFilter

refresh

addWidget

bind

hit

Widget

widgets.QueryInput

constructor

bind

widgets.Results

constructor

bind

widgets.ScrollResults

constructor

bind

widgets.TermFacet

constructor

bind

widgets.RangeFacet

constructor

bind

Client

constructor

search

Examples

Example 1: Create a simple template to show results.

Example 2: Adding extra info to our template.

Example 3: Create a custom template function.

Keywords

Related posts

Input Validation Vulnerabilities Dominate MITRE's 2024 CWE Top 25 List

Risky Business Podcast: Why Open Source Software Needs Better Malware Tracking