Interface DataManager

Closes the data manager. Any active connections are closed.

This function handles the data management aspects of the identification process.

Implementation Note: The identifyResolve and identifyReject function resolve or reject the identify function at LDClient level. It is likely in individual implementations that these functions will be passed to other components, such as a datasource, do indicate when the identify process has been completed. The data manager identify function should return once everything has been set in motion to complete the identification process.

Update the automatic streaming state based on whether change listeners are registered. When true and forced streaming is not set, the data manager should activate streaming.

Optional — only browser data managers implement this.

Set an explicit connection mode override. When set, only this mode is used, bypassing all automatic behavior. Pass undefined to clear the override.

Optional — only FDv2 data managers implement this.

Set a callback to flush pending analytics events. Called immediately (not debounced) when the lifecycle transitions to background.

Optional — only FDv2 data managers implement this.

Force streaming on or off. When true, the data manager should maintain a streaming connection. When false, streaming is disabled. When undefined, the forced state is cleared and automatic behavior takes over.

Optional — only browser data managers implement this.