🎉 Try the public beta of the new docs site at algolia.com/doc-beta! 🎉
UI libraries / Angular InstantSearch / Widgets

history

Angular InstantSearch isn’t compatible with Angular’s Ivy view engine. We’re investigating how best to support this. For more information and to vote for Algolia’s support of Angular 16 and beyond, see the GitHub issue Algolia Support for Angular InstantSearch

Signature 
import { history } from 'instantsearch.js/es/lib/routers';

history({
  // Optional parameters
  windowTitle: function,
  createURL: function,
  parseURL: function,
  writeDelay: number,
  getLocation: function,
  push: function,
  start: function,
  dispose: function,
});
See code examples

About this widget

The history router is the default for the ais-instantsearch object’s routing prop.

The router provides an API that lets you customize some of its behaviors. To get a sense of what you can do with the API, see the Routing URLs guide.

Examples

Copy 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

import { history } from 'instantsearch.js/es/lib/routers';

@Component({
  template: `
    <ais-instantsearch [config]="config">
      <!-- Widgets -->
    </ais-instantsearch>
  `
})
export class AppComponent {
  config = {
    // ...
    routing: {
      router: history()
    }
  };
}

Options

Parameter Description
windowTitle
type: function
Optional

This function lets you dynamically customize the window title based on the provided routeState. It’s called every time the user refines the UI and the history timer completes.
Copy 
1
2
3
4
5
6
7
8
9
10
11

history({
  windowTitle(routeState) {
    const indexState = routeState.indexName || {}

    if (!indexState.query) {
      return 'MyWebsite - Results page'
    }

    return `MyWebsite - Results for: ${indexState.query}`
  },
});
createURL
type: function
Optional

This function lets you directly change the format of URLs that are created and rendered for the browser URL bar or widgets. It’s called every time InstantSearch needs to create a URL. The provided options are:

  • qsModule (object): a module that can parse a query string or stringify an object. You can get more information from the qs documentation.
  • location (object): an alias to the implementation defined in getLocation. By default, it returns window.location.
  • routeState (object): the routeState created by the provided stateMapping. When absent, this is an untouched uiState.
Copy 
1
2
3
4
5
6
7
8
9
10
11
12
13

history({
  createURL({ qsModule, location, routeState }) {
    const { origin, pathname, hash } = location;
    const indexState = routeState || {};
    const queryString = qsModule.stringify(routeState);

    if (!indexState.query) {
      return `${origin}${pathname}${hash}`;
    }

    return `${origin}${pathname}?${queryString}${hash}`;
  },
});
parseURL
type: function
Optional

This function is responsible for parsing the URL string back into a routeState. It must be customized if you customized the createURL function. It’s called every time a user loads or reloads a page, or when they click on the back or next buttons of the browser. The provided options are:

  • qsModule (object): a module that can parse a query string or stringify an object. You can get more information from the qs documentation.
  • location (object): an alias to the implementation defined in getLocation. By default, it returns window.location.
Copy 
1
2
3
4
5

history({
  createURL({ qsModule, location }) {
    return  return qsModule.parse(location.search.slice(1));
  },
});
writeDelay
type: number
default: 400
Optional

This option controls the number of milliseconds the router waits before writing the new URL to the browser. You can think about it this way: “400 ms after the last user action, the URL is pushed to the browser”. This helps reduce:

  1. The number of different history entries. If you type “phone”, you don’t want to have 5 history entries and thus have to click 5 times on the back button to go back to the previous search state
  2. The performance overhead of updating the browser URL too often. There are recurring but hard to track performance issues associated with updating the browser URL too often: these issues result from browser extensions reacting to every change.

400 ms is a typically a pretty good writeDelay.
Copy 
1
2
3

history({
  writeDelay: 400,
});
getLocation
type: function
default: () => window.location
Optional

This function lets you return a custom implementation of Location. It enables support for routing in server environments where window isn’t available.

By default, it generates an error if there isn’t a custom implementation outside a browser environment.
Copy 
1
2
3
4
5
6
7
8
9
10

  history({
    getLocation() {
      if (typeof window === 'undefined') {
        const url = '...'; // retrieved from the server context
        return new URL(url) as unknown as Location;
      }

      return window.location;
    },
  });
push
type: function
Optional

This function lets you customize the behavior of the router when it pushes a new URL so that you can delegate it to a third party router or set a custom history state. It’s called every time the user refines the UI and the history timer completes. The provided option is:

  • url (string): the URL which needs to be pushed to the browser.
Copy 
1
2
3
4
5

  history({
    push(url) {
      thirdPartyRouter.push(url);
    }
  });
start
type: function
Optional

This function is called when the router starts. You can use it to synchronize InstantSearch’s router with a third party router by hooking events to it. The provided option is:

  • onUpdate: () => void: a function that needs to call to inform InstantSearch that the URL has changed.
Copy 
1
2
3
4
5
6
7

  history({
    start(onUpdate) {
      thirdPartyRouter.addEventListener('routeChange', () => {
        onUpdate();
      });
    }
  });
dispose
type: function
Optional

This function is called when the router gets disposed of. You can use it to detach events you may have set in start. The provided option is:
Copy 
1
2
3
4
5
6
7
8
9
10
11

  let handler;

  history({
    start(onUpdate) {
      handler = () => onUpdate();
      thirdPartyRouter.addEventListener('routeChange', handler);
    },
    dispose() {
      thirdPartyRouter.removeEventListener('routeChange', handler);
    }
  });
Did you find this page helpful?
Angular InstantSearch v4