Hierarchy

  • LDIdentifyOptions

Properties

noTimeout?: boolean

When set to true, and timeout is not set, this indicates that the identify operation will not have any timeout. In typical usage, where an application awaits the promise, a timeout is important because identify can potentially take indefinite time depending on network conditions. If your application specifically does not block any operations pending the promise resolution, then you can use this opton to explicitly indicate that.

If you set this to true, and you do not set a timeout, and you block aspects of operation of your application, then those aspects can be blocked indefinitely. Generally this option will not be required.

timeout?: number

In seconds. Determines when the identify promise resolves if no flags have been returned from the network. If you use a large timeout and await it, then any network delays will cause your application to wait a long time before continuing execution.

Defaults to 5 seconds.

waitForNetworkResults?: boolean

When true indicates that the SDK will attempt to wait for values from LaunchDarkly instead of depending on cached values. The cached values will still be loaded, but the promise returned by the identify function will not resolve as a result of those cached values being loaded. Generally this option should NOT be used and instead flag changes should be listened to. If the client is set to offline mode, then this option is ignored.

Defaults to false.

Generated using TypeDoc