Issue with context typing

[sinedied]

Hey @rohit-ganguly I bumped into an issue today because of this typing:

interface AIChatCompletionOptions {
    context?: object;
    sessionState?: unknown;
}

Because of the object type, you can't index it on arbitrary property as TypeScript reports an error. Some linters like @typescript-eslint reports an error because of this type too.

The same issue also exists with the other context occurrences in AIChatCompletion, AIChatCompletionDelta, AIChatMessage, AIChatMessageDelta.

I recommend updating the type from object to Record<string, unknown> which solves the issues above. This is a common type used in TS for generic indexable objects.

[sinedied]

My bad, I was using an older alpha version and npm outdated doesn't report me the newest version (which might be an issue!).

The latest version has the fixed types :)

[sinedied]

Reopening, as something's weird: I downloaded the latest beta as it still has object for the context type, event though the source code has the fixed code: https://github.com/microsoft/ai-chat-protocol/blob/main/sdk/js/packages/client/src/model/model.ts#L8

@rohit-ganguly would it be possible to publish a new version with the fixed types? It seems the commit that fixes it was made after the currently published version on NPM.