Most applications will not need to refer to these types. You will use them if you are creating a plugin component, such as a database integration. They are also used as interfaces for the built-in SDK components, so that plugin components can be used interchangeably with those.
The package also includes concrete types that are used as parameters within these interfaces.
Interface Summary Interface Description Callback<T>General-purpose interface for callbacks that can succeed or fail. ComponentConfigurer<T>The common interface for SDK component factories and configuration builders. DataSourceInterface for an object that receives updates to feature flags from LaunchDarkly. DataSourceUpdateSinkInterface that an implementation of
DataSourcewill use to push data into the SDK.
DiagnosticDescriptionOptional interface for components to describe their own configuration. EventProcessorInterface for an object that can send or store analytics events. PersistentDataStoreInterface for a data store that holds feature flag data and other SDK properties in a simple string format.
Class Summary Class Description ApplicationInfoEncapsulates the SDK's application metadata. ClientContextConfiguration information provided by the
LDClientwhen creating components.
HttpConfigurationEncapsulates top-level HTTP configuration that applies to all SDK components.