Integration
Wiring the client, bootstrap, and cross-cutting interceptors, pipes, services and utilities into a host application.
The pieces every application wires in once, regardless of which search features it uses: the client connecting to the backend, the bootstrap sequence that signs the user in, and the interceptors, pipes, services and utilities that cut across every feature rather than belonging to one.
What's next
Provide a client
Give the application its own Sinequa client instead of the default one.
Serve a second backend
A route or component subtree with its own client, stores and services.
Notify failed requests as toasts
Surface a failed request without wrapping HttpClient.
Bootstrap the application
Sign the user in and initialize the application's stores.
Cross-cutting interceptors
The interface language, audit metadata and 401 recovery, on the HttpClient channel.
Cross-cutting pipes
Legacy filter display, translated system strings, locale-aware dates, file sizes, highlighting.
Cross-cutting utilities
Building a query from the route, a Web Worker wrapper, a baseline fetch wrapper.
Cross-cutting services
Registering route components, custom audit events, JsonMethod plugin calls.
Default query name resolver
Supplies the application's default query name to a route with no explicit one.
Toast interceptor
An HttpInterceptorFn that turns a failed HttpClient request into a toast for the status codes worth telling the user about, without wrapping HttpClient itself.
Provide a client
Give an application its own Sinequa client — its own configuration, session and event subscribers — instead of the default one backing the free functions.