-
Notifications
You must be signed in to change notification settings - Fork 230
Open
Description
This is the latest implementation of the TaskDefinition model:
llama_deploy/llama_deploy/types/core.py
Lines 106 to 125 in ac927e6
| class TaskDefinition(BaseModel): | |
| """ | |
| The definition and state of a task. | |
| Attributes: | |
| input (str): | |
| The task input. | |
| session_id (str): | |
| The session ID that the task belongs to. | |
| task_id (str): | |
| The task ID. Defaults to a random UUID. | |
| service_id (str): | |
| The service ID that the task should be sent to. | |
| If blank, the orchestrator decides. | |
| """ | |
| input: str | |
| task_id: str = Field(default_factory=generate_id) | |
| session_id: str | None = None | |
| service_id: str | None = None |
The description for input appears very confusing to me. input (str): The task input. suggests being a regular string (i.e., query to a workflow), but apparently it is actually expecting a JSON encoded string.
From this description alone, I could not deduce what it does or expects. Correct me if I'm wrong – is this just the serialized input that is eventually processed by a workflow's run method?
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
No status