Visitor 1.0.0 API

All Implemented Interfaces:


public interface EvalCreateParams.DataSourceConfig.Visitor<T extends Object>

An interface that defines how to map each variant of DataSourceConfig to a value of type T.

Nested Class Summary

Nested Classes
Modifier and Type	Class	Description

Field Summary

Fields
Modifier and Type	Field	Description

Constructor Summary

Constructors
Constructor	Description

Enum Constant Summary

Enum Constants
Enum Constant	Description

Method Summary

Modifier and Type	Method	Description
`abstract T`	`visitCustom(EvalCreateParams.DataSourceConfig.Custom custom)`	A CustomDataSourceConfig object that defines the schema for the data source used for the evaluation runs.
`abstract T`	`visitStoredCompletions(EvalCreateParams.DataSourceConfig.StoredCompletions storedCompletions)`	A data source config which specifies the metadata property of your stored completions query.
`T`	`unknown(JsonValue json)`	Maps an unknown variant of DataSourceConfig to a value of type T.

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- Constructor Detail
- Method Detail
  - visitCustom
```
 abstract T visitCustom(EvalCreateParams.DataSourceConfig.Custom custom)
```
    A CustomDataSourceConfig object that defines the schema for the data source used for the evaluation runs. This schema is used to define the shape of the data that will be:
    Used to define your testing criteria and
    What data is required when creating a run
  - visitStoredCompletions
```
 abstract T visitStoredCompletions(EvalCreateParams.DataSourceConfig.StoredCompletions storedCompletions)
```
    A data source config which specifies the metadata property of your stored completions query. This is usually metadata like usecase=chatbot or prompt-version=v2, etc.
  - unknown
```
 T unknown(JsonValue json)
```
    Maps an unknown variant of DataSourceConfig to a value of type T.
    An instance of DataSourceConfig can contain an unknown variant if it was deserialized from data that doesn't match any known variant. For example, if the SDK is on an older version than the API, then the API may respond with new variants that the SDK is unaware of.