data

func NewClientSideFlagFactory ¶

func NewClientSideFlagFactory(
	keyPrefix string,
	valueFactory ValueFactoryBySDKValueType,
	builderActions ...func(*mockld.ClientSDKFlagWithKey),
) *ClientSideFlagFactory

NewClientSideFlagFactory creates a ClientSideFlagFactory with the specified configuration.

The valueFactory parameter provides the value that each flag will return for evaluations. The builderActions, if any, will be run each time a flag is created. Each flag will have a unique key beginning with the specified prefix.

func NewContextFactoriesForExercisingAllAttributes ¶

func NewContextFactoriesForExercisingAllAttributes(
	prefix string,
) []*ContextFactory

NewContextFactoriesForExercisingAllAttributes produces a list of ContextFactory instances that use different subsets of the context schema, to verify that context attributes are encoded correctly when they are sent to evaluation endpoints.

The returned list will include factories for 1. single-kind Contexts with no attributes other than kind and key, 2. single-kind Contexts with every possible kind of attribute, 3. multi-kind Contexts that combine 1 and 2.

Each will have an appropriate Description, so the logic for running a test against each one can look like this:

for _, contexts := range data.NewContextFactoriesForExercisingAllAttributes("NameOfTest") {
    t.Run(contexts.Description(), func(t *testing.T) {
        context := contexts.NextUniqueContext() // do something with this
    })
}

func NewContextFactoriesForSingleAndMultiKind ¶

func NewContextFactoriesForSingleAndMultiKind(
	prefix string, builderActions ...func(*ldcontext.Builder),
) []*ContextFactory

NewContextFactoriesForSingleAndMultiKind produces a list of ContextFactory instances for testing SDK functionality that may behave differently for different Context variants.

The returned list will include factories for 1. single-kind Contexts of the default kind, 2. single-kind Contexts of a different kind, 3. multi-kind Contexts. The reason for checking single vs. multi-kind is that we want to make sure the SDK correctly enumerates the kinds when it populates the contextKeys property in event data. The reason for checking the default kind vs. a non-default kind is that it affects the deduplication logic for index events.

Each will have an appropriate Description, so the logic for running a test against each one can look like this:

for _, contexts := range data.NewContextFactoriesForSingleAndMultiKind("NameOfTest") {
    t.Run(contexts.Description(), func(t *testing.T) {
        context := contexts.NextUniqueContext() // do something with this
    })
}

func NewContextFactory ¶

func NewContextFactory(prefix string, builderActions ...func(*ldcontext.Builder)) *ContextFactory

NewContextFactory creates a ContextFactory that produces single-kind Contexts.

Each generated Context will have a unique key that starts with the prefix string. The builderActions, if any, will be run against the builder for each Context. If no actions are specified, then it will have no properties other than the key, and its kind will be ldcontext.DefaultKind ("user").

func NewMultiContextFactory ¶

func NewMultiContextFactory(
	prefix string,
	kinds []ldcontext.Kind,
	builderActions ...func(*ldcontext.Builder),
) *ContextFactory

NewMultiContextFactory creates a ContextFactory that produces multi-kind Contexts.

Each generated multiple context will contain an individual context for each of the kinds in the kinds parameter. If builderActions are specified, the first one will be run for the first kind, the second for the second, etc. Each individual context will have a unique key that starts with the prefix string.

func NewFlagFactory ¶

func NewFlagFactory(
	keyPrefix string,
	valueFactory ValueFactoryBySDKValueType,
	builderActions ...func(*ldbuilders.FlagBuilder),
) *FlagFactory

NewFlagFactory creates a FlagFactory with the specified configuration.

The valueFactory parameter provides the value that each flag will return for evaluations. The builderActions, if any, will be run each time a flag is created. Each flag will have a unique key beginning with the specified prefix.

func NewMemoizingClientSideFlagFactory ¶

func NewMemoizingClientSideFlagFactory(
	startingVersion int,
	factoryFn func(servicedef.ValueType) mockld.ClientSDKFlagWithKey,
) *MemoizingFactory[servicedef.ValueType, mockld.ClientSDKFlagWithKey]

func NewMemoizingFlagFactory ¶

func NewMemoizingFlagFactory(
	startingVersion int,
	factoryFn func(servicedef.ValueType) ldmodel.FeatureFlag,
) *MemoizingFactory[servicedef.ValueType, ldmodel.FeatureFlag]

func LoadAllDataFiles ¶

func LoadAllDataFiles(path string) ([]SourceInfo, error)

LoadAllDataFiles reads all data files in a directory and performs any necessary constant/parameter substitutions. It can return more than one SourceInfo per file, because any file can be a parameterized test. See docs/data_files.md.

The path parameter is relative to data/data-files.

func LoadDataFile ¶

func LoadDataFile(path string) ([]SourceInfo, error)

LoadDataFile reads a data file and performs any necessary constant/parameter substitutions. It can return more than one SourceInfo because any file can be a parameterized test. See docs/data_files.md.

The path parameter is relative to data/data-files.

func MakeValueFactoriesBySDKValueType ¶

func MakeValueFactoriesBySDKValueType(howMany int) []ValueFactoryBySDKValueType

MakeValueFactoriesBySDKValueType creates the specified number of ValueByTypeFactory generators, each producing different values from the others (insofar as possible, given that there are only two possible values for the boolean type).

func MakeValueFactoryBySDKValueType ¶

func MakeValueFactoryBySDKValueType() ValueFactoryBySDKValueType

MakeValueFactoryBySDKValueType creates a ValueByTypeFactory generator providing a different value for each servicedef.ValueType.

func SingleValueForAllSDKValueTypes ¶

func SingleValueForAllSDKValueTypes(value ldvalue.Value) ValueFactoryBySDKValueType

SingleValueForAllSDKValueTypes creates a ValueByTypeFactory generator that always returns the same value.