Class DataModel

Contains information about the internal data model for feature flags and user segments.

Inheritance

object

DataModel

Inherited Members

object.Equals(object)

object.Equals(object, object)

object.GetHashCode()

object.GetType()

object.MemberwiseClone()

object.ReferenceEquals(object, object)

object.ToString()

Namespace: LaunchDarkly.Sdk.Server

Assembly: LaunchDarkly.ServerSdk.dll

Syntax

public static class DataModel

Remarks

The details of the data model are not public to application code (although of course developers can easily look at the code or the data) so that changes to LaunchDarkly SDK implementation details will not be breaking changes to the application. Therefore, most of the members of this class are internal. The public members provide a high-level description of model objects so that custom integration code or test code can store or serialize them.

Fields

Features

The DataStoreTypes.DataKind instance that describes feature flag data.

Declaration

public static DataStoreTypes.DataKind Features

Field Value

Type	Description
DataStoreTypes.DataKind

Remarks

Applications should not need to reference this object directly. It is public so that custom integrations and test code can serialize or deserialize data or inject it into a data store.

Segments

The DataStoreTypes.DataKind instance that describes user segment data.

Declaration

public static DataStoreTypes.DataKind Segments

Field Value

Type	Description
DataStoreTypes.DataKind

Remarks

Applications should not need to reference this object directly. It is public so that custom integrations and test code can serialize or deserialize data or inject it into a data store.

Properties

AllDataKinds

An enumeration of all supported DataStoreTypes.DataKinds.

Declaration

public static IEnumerable<DataStoreTypes.DataKind> AllDataKinds { get; }

Property Value

Type	Description
IEnumerable<DataStoreTypes.DataKind>

Remarks

Applications should not need to reference this object directly. It is public so that custom data store implementations can determine ahead of time what kinds of model objects may need to be stored, if necessary.