Zod validation errors when using streaming with functions/tools

[jpaquim]

Started getting this error after the upgrade (after fixing any breaking changes I could identify):

ZodError: [
  {
    "code": "invalid_type",
    "expected": "string",
    "received": "null",
    "path": [
      "data",
      "choices",
      0,
      "delta",
      "content"
    ],
    "message": "Expected string, received null"
  },
  {
    "code": "invalid_literal",
    "expected": "function",
    "path": [
      "data",
      "choices",
      0,
      "delta",
      "tool_calls",
      0,
      "type"
    ],
    "message": "Invalid literal value, expected \"function\""
  }
]
    at get error [as error] (<dir>/node_modules/.pnpm/[email protected]/node_modules/zod/lib/types.js:55:31)
    at ZodObject.parse (<dir>/node_modules/.pnpm/[email protected]/node_modules/zod/lib/types.js:160:22)
    at decoder (<dir>/node_modules/.pnpm/@[email protected][email protected]/node_modules/@mistralai/mistralai/funcs/chatStream.js:96:31)
    at parseEvent (<dir>/node_modules/.pnpm/@[email protected][email protected]/node_modules/@mistralai/mistralai/lib/event-streams.js:149:12)
    at [Symbol.asyncIterator] (<dir>/node_modules/.pnpm/@[email protected][email protected]/node_modules/@mistralai/mistralai/lib/event-streams.js:42:35)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Object.start (<dir>/src/lib/server/streams.ts:13:28)

[GaspardBT]

Thank you for testing and reporting this issue.
This PR #15 will address the issue "message": "Invalid literal value, expected \"function\"", the other one will be address by #16

[jpaquim]

Thank you @GaspardBT 👍 do you happen to have an estimate for when these changes will be published to npm?

[GaspardBT]

It will be once this PR is merged 👍 (soon hopefully)