What happened?
The 1.0 Client SDK and the Server SDK differ in what they expect task objects to look like. The client expects a list of task to be as follows:
"tasks": [ { "id": "someId", "contextId": "contextId", ... } ]
But the server actually serves back the following with an extra object wrapper around the task fields:
"tasks": [ { "task": { "id": "someId", "contextId": "contextId", ... } } ]
And according to the task spec it would seem the client is correct and the issue comes in around the way the "StreamingEventKind" with the STREAMING_EVENT_ID = "task" is applied to the response objects returned from the server implementation.
Relevant log output
Code of Conduct
What happened?
The 1.0 Client SDK and the Server SDK differ in what they expect task objects to look like. The client expects a list of task to be as follows:
"tasks": [ { "id": "someId", "contextId": "contextId", ... } ]But the server actually serves back the following with an extra object wrapper around the task fields:
"tasks": [ { "task": { "id": "someId", "contextId": "contextId", ... } } ]And according to the task spec it would seem the client is correct and the issue comes in around the way the "StreamingEventKind" with the STREAMING_EVENT_ID = "task" is applied to the response objects returned from the server implementation.
Relevant log output
Code of Conduct