chore: port ResultType fix (#4)
https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2773
This commit is contained in:
parent
29f83d5c8b
commit
104a270d5f
2 changed files with 2 additions and 2 deletions
|
|
@ -98,7 +98,7 @@ A request that is eligible for task-augmentation may return one of two distinct
|
|||
|
||||
```typescript
|
||||
// "task" is introduced by this extension.
|
||||
type ResultType = "complete" | "input_required" | "task";
|
||||
type ResultType = "complete" | "input_required" | "task" | string;
|
||||
```
|
||||
|
||||
Servers **MUST** set `resultType` to `"task"` when returning a `CreateTaskResult` so that clients can distinguish it from a standard result. Servers **MUST NOT** set `resultType` to `"task"` on result types other than `CreateTaskResult`.
|
||||
|
|
|
|||
|
|
@ -122,7 +122,7 @@ A request that is eligible for task-augmentation may return one of two distinct
|
|||
|
||||
```typescript
|
||||
// "task" is introduced by this extension.
|
||||
type ResultType = "complete" | "input_required" | "task";
|
||||
type ResultType = "complete" | "input_required" | "task" | string;
|
||||
```
|
||||
|
||||
Servers **MUST** set `resultType` to `"task"` when returning a `CreateTaskResult` so that clients can distinguish it from a standard result. Servers **MUST NOT** set `resultType` to `"task"` on result types other than `CreateTaskResult`.
|
||||
|
|
|
|||
Loading…
Reference in a new issue