Integration

Fitting the library into a host — transports, logging, localisation, telemetry, and testing it without module mocks.

Cross-cutting concerns: everything that is not a Sinequa feature but decides how the library behaves inside your application.

Calling an endpoint with no typed wrapper, and the per-request options every call accepts.

Two servers on one page, and the storage prefix that keeps their sessions apart.

Two applications on the same server — two configurations, one shared session.

The ./spfx entry point, and why a web part must route through the host's client.

Replacing fetch — for retries, tracing, or a host that owns the network.

Telling the server which language to answer in, and decoding the labels it returns.

The event contract the library uses to surface messages without importing a UI.

configureLogger, and why the console blames your code rather than the library.

Usage telemetry, what it carries, and what it feeds.

Containers of user-uploaded documents, their roles and their locks.

Injecting fetch, storage and logger — no module mocks required.