Identify pipeline entries in reports and diagnostics
This commit is contained in:
@@ -11,12 +11,14 @@ import (
|
||||
|
||||
// DiagnosticContext identifies the logical call without examining rendered text.
|
||||
type DiagnosticContext struct {
|
||||
Role string `json:"role"`
|
||||
ModuleKey string `json:"module_key,omitempty"`
|
||||
ModuleInstance string `json:"module_instance,omitempty"`
|
||||
SectionIndex *int `json:"section_index,omitempty"`
|
||||
BatchIndex *int `json:"batch_index,omitempty"`
|
||||
ValidatorName string `json:"validator_name,omitempty"`
|
||||
StageIndex *int `json:"stage_index,omitempty"`
|
||||
StageID *string `json:"stage_id,omitempty"`
|
||||
Role string `json:"role"`
|
||||
ModuleKey string `json:"module_key,omitempty"`
|
||||
ModuleInstance string `json:"module_instance,omitempty"`
|
||||
SectionIndex *int `json:"section_index,omitempty"`
|
||||
BatchIndex *int `json:"batch_index,omitempty"`
|
||||
ValidatorName string `json:"validator_name,omitempty"`
|
||||
}
|
||||
|
||||
// Request names an embedded prompt and response schema. Profile selection and
|
||||
|
||||
Reference in New Issue
Block a user