This is the API reference for the LaunchDarkly SDK for Electron.
In typical usage, you will call initializeInMain in the main process at startup time to obtain an instance of LDElectronMainClient-- and, optionally, call initializeInRenderer in a renderer process to obtain a corresponding instance of LDElectronRendererClient.
For more information, see the SDK reference guide.
The types of values a feature flag can have.
Flags can have any JSON-serializable value.
The current version string of the SDK.
A basic implementation of logging that uses the global
console object. This is used by
default in the browser SDK. It sends messages of "debug", "info", "warn", or "error"
level (if enable) to
To make LDClient use this logger, put it in the
logger property of LDOptions.
Wraps an instance of the LaunchDarkly Electron main-process client with an alternate interface that is the same as the LaunchDarkly Node SDK. This is intended to make it easier to port LaunchDarkly-enabled Node.js code to Electron.
An instance of LDElectronNodeAdapterClient that controls the same SDK client.
Creates an instance of the LaunchDarkly Electron client to be used in the main process.
The LaunchDarkly environment ID.
The initial user properties. These can be changed later with LDElectronMainClient.identify.
Optional configuration settings.
Creates an instance of the LaunchDarkly Electron client to be used in a renderer process, which will receive all of its state from a client in the main process.
The LaunchDarkly environment ID. This can usually be omitted because it can be obtained from the LDElectronMainClient instance in the main process. You only need to specify it here if there are multiple client instances with different environment IDs.
Optional configuration settings. Since the main process client controls all communication with
LaunchDarkly, the only options that can actually be set for the renderer client are the ones that
control event generation:
Generated using TypeDoc